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
- 1540 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 |
Which jms standard interface defines the methods to create the different types of messages?
Explain about session interface?
What is the difference between Jms and Jvt ?
What is difference between jms and activemq?
Why doesn’t the JMS API provide end-to-end synchronous message delivery and notification of delivery?
Is jms a protocol?
What are jms topics and queues?
Which are the benefits of mdb (message driven beans) over standard jms consumers?
What is the important part of JMS applications?
What type messaging is provided by JMS ?
What are the various message types supported by JMS?
How does spring jms listener work?
Core Java 
