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
- 2435 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
What is message listener container?
What is a connection factory?
In which situations we are using jms?
Which jms standard interface defines the methods to create the different types of messages?
What is jms testing?
Detail about the features of publish model?
What is a topic string?
Can you use a foreign jms provider to drive an mdb transactionally?
What is jms consumer?
What is the difference between java mail and jms queue?
How you can deliver a java message to a non-java client?
Explain Synchronous Message Consumption in JMS?
What is a jms server?
How do I configure jms security?
What are jms channels?
