Interested to Buy Any Domain ? << Click Here >> for more details...
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?
- 1 Answers
- 2470 Views
- I also Faced
- E-Mail Answers
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
Explain about the exception handling mechanism of JMS?
Why do we use jms?
What are the three parts of the message?
How kafka is different from jms?
Can jms be used to send an email?
What is jms broker in sas?
How does spring jms listener work?
What does kms mean?
Detail about the features of publish model?
Is rabbitmq jms compliant?
How the jms is different from rpc?
How do I configure jms security?
How do I use a startup class to initialize and later reference jms objects?
What is jms destination?
How can an application do a jms operation and have it succeed, independent of the result of the transaction?
