Skip to main content

API-based connections cause "There are no available slots on the cluster named..." errors. How can this be resolved?




When using Kapow's API to create connections to MC using Java, the error above is displayed even though MC shows plenty of licenses, regardless of KCU or CRE-based licensing. How can this be resolved?


This is by design and is not a software issue. When using Kapow API's, there is a twenty-connection limit. When an RS node is registered to MC, one connection is used, therefore nineteen remain. Each JVM connection takes up one connection. Kapow is designed to support one connection per client. Allowing more than twenty may introduce performance issues.



  • Was this article helpful?