JMS Queue Caused Stuck Threads In Managed Servers
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.4 and later
Information in this document applies to any platform.
***Checked for relevance on 4-Nov-2014***
Managed Servers hung with blocked threads in the production server.
When a remote server hosting a destination goes down or becomes unresponsive, the JMSConnectionPoller used to test and maintain connections for deployed MDB has to reset and recreate connections. When the disconnection is detected, the JMSConnectionPoller attempts to stop and cleanup the associated sessions. But this stop of the session takes a lot longer while holding lock on the JMSConnectionPoller and other threads that detect the disconnection also attempt to get lock on the same JMSConnectionPoller leading to bottleneck in heavily loaded server instances where multiple threads get blocked and cannot do faster recovery in case of disconnections.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms