Interested to Buy Any Domain ? << Click Here >> for more details...
Why do the TopicSession.createDurableSubscriber and TopicSession.unubscribe calls raise JMSException with the message "ORA - 4020 - deadlock detected while trying to lock object"?
- 1 Answers
- 2156 Views
- I also Faced
- E-Mail Answers
Answer / munnu
CreateDurableSubscriber and unsubscribe calls require exclusive access to the Topics. If there are pending JMS operations (send/publish/receive) on the same Topic before these calls are issued, the ORA - 4020 exception is raised.
There are two solutions to the problem:
1. Try to isolate the calls to createDurableSubscriber and unsubscribe at the setup or cleanup phase when there are no other JMS operations happening on the Topic. That will make sure that the required resources are not held by other JMS operational calls. Hence the error ORA - 4020 will not be raised.
2. Issue a TopicSession.commit call before calling createDurableSubscriber and unsubscribe call.
| Is This Answer Correct ? | 0 Yes | 0 No |
Explain how Application server handles the JMS Connection?
What are Messages?
What is Point-to-Point Approach?
What is difference between queue and topic in jms?
How to Allowe messages to expire ?
How do I find the jms queue in weblogic?
What is spring jms?
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 administered objects in jms?
What are the different types of messaging systems?
Why do we need jms?
What is the Role of the JMS Provider?
Core Java 
