JMSReceiver Connections To MQSeries Using JAVA64 Subsystem Are Not Closed Leaving Many Open Connections With CLOSE_WAIT Status
(Doc ID 2791187.1)
Last updated on JULY 13, 2021
Applies to:
Siebel CRM - Version 20.9 and laterInformation in this document applies to any platform.
Symptoms
When using Siebel JMSReceiver to connect to MQSeries 6.0, the connections to the MQSeries server are not getting closed out, the connection remains in CLOSE_WAIT status. Additionally, the number of connections in CLOSE_WAIT status continues to increase since they are not getting closed out, causing the MQ channel limit to be reached quickly, to the point where new connections cannot be established as a result and generating an error
For example, the following netstat command shows that connections to the MQSeries server with IP and port 2424 (xx.xxx.xxx.xxxx.2424) are all in CLOSE_WAIT status from different client calls:
netstat -an | grep xx.xxx.xxx.xxxx | grep CLOSE
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |