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
- 1559 Views
- I also Faced
- E-Mail Answers
Answer Posted / 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 |
Post New Answer View All Answers
What is mean by jms?
What are the steps to send and receive JMS message ?
What is the difference between Jms and Jvt ?
What is message listener container?
What is a remote jms provider?
What is the functionality of a jms message selector?
Is jms a protocol?
What is jms protocol?
What is jms used for?
What is a jms listener?
Can we use jms for sending automated e-mails?
What is jms and mq?
How do I use a startup class to initialize and later reference jms objects?
What is a queued message?
Explain Asynchronous Message Consumption in JMS?
