| Summary | How to limit the number of new incoming iiop connections to an Orbix server? |
|---|---|
| Article Number | 19509 |
| Environment | All Supported Operating Systems Orbix 6.3 |
| Question/Problem Description | How to limit the number of new incoming IIOP connections to an Orbix server? How to configure active connection management in Orbix 6 How does Orbix handle new incoming connections to a server if the plugins:iiop:incoming_connections:hard_limit has been reached? |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution |
Orbix active connection management (ACM) lets servers scale up to large numbers of clients without encountering connection limits. Using active connection management, Orbix recycles least recently used connections as new connections are required. You can control active connection management in Orbix with configuration variables, that specify the maximum number of incoming and outgoing client-server connections. Two settings are available for both client-side and server-side connections: Active Connection Management in Orbix can be configured through the following configuration variables:
plugins:iiop:incoming_connections:hard_limit specifies the maximum number of incoming (server-side) connections permitted to IIOP. IIOP does not accept new connections above this limit. Defaults to -1 (disabled). |
| Workaround | |
| Notes | If on the server side the configured plugins:iiop:incoming_connections:hard_limit is reached the client logs a "IT_GIOP:REMOTE_CONNECTION_CLOSED" warning. Once the soft limit is reached the ORB will start to close the least recently used (not necessarily the oldest) connections to accept new connections. |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 12 February 2013 |
| Last Published: | 28 November 2012 |
| First Published date: | 10 September 2011 |
#Orbix
#KnowledgeDocs