Interested to Buy Any Domain ? << Click Here >> for more details...
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
- 2061 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 |
What is a jms queue?
What are the components of JMS?
What does kms mean?
What are the different messaging paradigms JMS supports?
What is jms in websphere?
What is the difference between Point to Point and Publish/Subscribe Point-to-point (P2P)
What is the difference between BytesMessage and StreamMessage?
What is JMS administered object?
What is jms connection?
What is jms in spring?
How can third-party jdbc driver be used with jms?
Can JMS utilities automatically re-establish a connection if one side of the communication link (i.e. an application that's sending/receiving messages) goes down and is restarted? Are there APIs to help detect that the other side broke a connection (went down)?
Core Java 
