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
- 2555 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 |
How do I configure jms security?
Which messaging is generally used in cases where a message is published by a producer and consumed by multiple subscribers?
What are Messaging Domains?
What is Map message?
What is Producer and Consumer?
Explain about message listeners?
What is JMS API Architecture?
What is spring jms?
What is jms in java with example?
Can two different jms services talk to each other? For instance, if a and b are two different jms providers, can provider a send messages directly to provider b? If not, then can a subscriber to provider a act as a publisher to provider b?
What is a topic?
What type messaging is provided by JMS ?
Core Java 
