Deadlock Between MessageQueue DirectionConnection And DirectionSession When Running In Embedded Mode In Oracle GlassFish Server
(Doc ID 1453671.1)
Last updated on FEBRUARY 20, 2025
Applies to:
Oracle GlassFish Server - Version 3.1.1 and laterInformation in this document applies to any platform.
Symptoms
The GlassFish Server process hangs processing JMS Messages in Message Driven Beans (MBDs). The problem can only occur when running the Message Queue (MQ) Broker in Embedded mode, that is in-process with the GlassFish Server in a single Java runtime.
The Java Runtime reports a deadlock between DirectQueueSession and DirectionConnection objects:
Changes
This problem could be encountered if you switch to the MQ Embedded mode, though this mode is the normal default in GlassFish Server 3.x.
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 |