Troubleshooting
Problem
The number of connections in the LISTEN state is growing continuously. This can be seen by using a netstat command from a command line or from the contents of the perimeter server log file. The node eventually exhausts all available connections at which time it must be stopped and restarted.
Symptom
- A netstat command shows a local IP:port and no remote port or hostname for the Listen connection.
- The listen connection port can be matched to the noapp pid.
- There are no server adapters configured with the port number indicated.
- There is a new connection initiated by the load balancer that fails and has a source port matching the netstat local port in listening for each new connection of the growing number of connections.
- After a stop of the affected node, the connections disappear, but immediately resume growing in number when the node is restarted.
- "ERROR Relay[local]: Max concurrent circuits reached" eventually appears in perimeter server log unless the node is stopped and restarted prior to that.
[{"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"}],"Version":"5.2.5","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
20 November 2019
UID
swg21975428