Why do the TopicSession.createDurableSubscriber and TopicSession.unubscribe calls raise JMSException with the message "ORA - 4020 - deadlock detected while trying to lock object"?
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 |
How does spring jms listener work?
What is a message topic?
What is jms jndi?
Which models are supported by jms? Please, explain them.
Wat is jms client?
What is the use of jms server in weblogic?
How can an application do a jms operation and have it succeed, independent of the result of the transaction?
What are Messages?
what is distributed queues and topics and how they works
What is publish/subscribe messaging?
Can I Use XML to transform more than 10 mb of data? Trasnsfom inbetween two module/methods etc. If not how can I do.
Is rabbitmq a jms?