Dequeue From Multiconsumer Jms Queue Fails With Jms-199 Error.
(Doc ID 363203.1)
Last updated on JANUARY 13, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.5 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
There are a number MultiConsumer JMS Queues and a number of SingleConsumer JMS queues. Messages are getting dequeued by the Java Dequeueing client for both types mentioned above in the synchronous method of dequeueing. In the asynchronous listener mode, the java client is able to dequeue from the SingleConsumer Queue. But, the java client is not able to dequeue from the MultiConsumer Queue in the asynchronous mode.
Having separate dequeue users created for each of the queues mentioned above. When the queue
owner user was used to dequeue from java client, the following error was generated:
oracle.jms.AQjmsException: JMS-199: Registration for asynchronous receipt of
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