Why do the JMS dbms_aqadm.add_subscriber and dbms_aqadm.remove_subscriber calls sometimes hang when there are concurrent enqueues or dequeues happening on the same queue to which these calls are issued?
Answer / munnu
Add_subscriber and remove_subscriber are administrative operations on a queue. Though AQ does not prevent applications from issuing administrative and operational calls concurrently, they are executed serially. Both add_subscriber and remove_subscriber will block until pending transactions that have enqueued or dequeued messages commit and release the resources they hold. It is expected that adding and removing subscribers will not be a frequent event. It will mostly be part of the setup for the application. The behavior you observe will be acceptable in most cases. The solution is to try to isolate the calls to add_subscriber and remove_subscriber at the setup or cleanup phase when there are no other operations happening on the queue. That will make sure that they will not stay blocked waiting for operational calls to release resources.
| Is This Answer Correct ? | 0 Yes | 0 No |
How does spring jms listener work?
What is the difference between the P2P (Peer to Peer) model and subscribe model?
What are the core JMS-related objects required for each JMS-enabled application?
What Is Messaging?
Can you use a foreign jms provider to drive an mdb transactionally?
What is MOM in reference to JMS?
Explain the process of Configuring Queues in Jms?
Why do we need jms?
How do I check messages in jms queue?
Explain the difference between topic and queue?
For sending messages through JMS, what encryption options are there?
Why do I get java.security.AccessControlException when using JMS MessageListeners from Java stored procedures inside Oracle8i JServer?