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
- 2451 Views
- I also Faced
- E-Mail Answers
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 |
What are the core JMS-related objects required for each JMS-enabled application?
Why do we use message queue?
What type messaging is provided by JMS ?
What are the functionalities of a jms provider?
How do I check messages in jms queue?
How do I use a third-party jdbc driver with jms?
Are foreign destinations handled within foreign jms messages?
How do I find the jms queue in weblogic?
What is a message in software?
How can third-party jdbc driver be used with jms?
What is an object message?
Give an example of using the publish/subscribe model.
Core Java 
