Broken MQ Connections Are Not Cleaned Up From The Pool
(Doc ID 1530251.1)
Last updated on JULY 10, 2020
Applies to:Oracle Java CAPS Enterprise Service Bus - Version R6.3 and later
Information in this document applies to any platform.
Checked for relevance on 29-May-2015
The connection pool for an MQSeries eWay seems to be filled up with stale connections when an MQ managers is shut down.
This problem occurs after a GF application server establishes connections to an external system, the number of connections reaches the predefined maximum connection number for a connection pool and the external system is brought down and up again. Consequently, all connections in the connection pool become invalid and attempts to use them to connect to the external system causes exceptions to be thrown.
However the invalid connections are not removed from the connection pool, thus no new connection can be made since the number of connections is at the allowed maximum.
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