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
- 1548 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
How do I find the jms queue in weblogic?
How do I configure jdbc so that the jms jdbc store recovers automatically?
What is a topic?
What are the different places where you can use the JMS API?
Why jms is used in java?
Why do we use jms?
What is the difference between a queue and a topic?
Explain Asynchronous Message Consumption in JMS?
In which situations we are using jms?
Explain about message listeners?
What is wire level protocol?
Is ibm mq jms compliant?
Is activemq a jms provider?
What is jms consumer?
What is use of jms?
