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 is the important part of JMS applications?
What is the functionality of the oracle glassfish server? What added advantage it has on top of apache tomcat server?
What is the difference between Jms and Jvt ?
How to Configure Open JMS?
What is jms protocol?
What is Publish/Subscribe approach?
What is difference between JMS and Web Services?
What is jms message?
What is a jms server?
Can we send e-mail messages using JMS?
Mention the difference between durable and non-durable subscription?
What is a bytes message?
What is administered objects in jms?
What is jms connection factory?
How does a sender application transport/send a message through jms?