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 |
Which types of jdbc databases does weblogic jms support?
What is difference between JMS and Web Services?
What is meant by jms?
Is jms a message broker?
What is the difference between jms and mq?
How you can deliver a java message to a non-java client?
Give an example of using the point-to-point model
What is the use of StreamMessage?
What is mean by jms?
What is jms testing?
What do you mean by Synchronous and Asynchronous type of messaging?
What is mdb in jms?