Unable to Dequeue Messages from an Exception Queue When Using a JMS Message Selector
(Doc ID 746891.1)
Last updated on AUGUST 04, 2018
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.4 to 10.2.0.4 [Release 10.2]
Oracle Containers for J2EE - Version 10.1.3.3.0 to 10.1.3.3.0 [Release AS10gR3]
Information in this document applies to any platform.
A JMS Queue Receiver session hangs waiting to receive a message from an Exception Queue when using a JMS Message Selector or depending on the client and database versions returns with no message payload.
This can occur when using a JMS Message Selector based on MSGID or CORRELATIONID or a user defined message property.
Problem reproduces when using a 10.1.0.5 client and a 10.2.0.4 database or using an Oracle Application Server version which is based on 10.1.0.5.
Problem with the null message reproduces when using just a 10.2.0.4 database.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!