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
- 2163 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 |
Can you use a foreign jms provider to drive an mdb transactionally?
Where is jms used?
What are the main component in JMS?
What is hermes software?
What is jms connection?
What is jms and how it works?
How do I use a third-party jdbc driver with jms?
What is the use of MapMessage?
How does the Application server handle the JMS Connection?
What are Native Clients ?
What are the different messaging paradigms JMS supports?
What is Map message?
Core Java 
