Deadlock Between MessageQueue DirectionConnection And DirectionSession When Running In Embedded Mode In Oracle GlassFish Server
Last updated on NOVEMBER 05, 2016
Applies to:Oracle GlassFish Server - Version 3.1.1 and later
Information in this document applies to any platform.
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:
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.
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