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 Posted / 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 |
Post New Answer View All Answers
What happens when jms queue is full?
Explain about session interface?
What are the different parts of a jms message?
What are jms channels?
What is use of jms?
What is jms template?
What is the number of messaging models available on jms?
Are foreign destinations handled within foreign jms messages?
What is jms broker in sas?
What is jms testing?
What is jms and mq?
What are the steps involved in configuring the jms?
How to Allowe messages to expire ?
Explain the difference between topic and queue?
What is the use of jms?