Why do the TopicSession.createDurableSubscriber and TopicSession.unubscribe calls raise JMSException with the message “ORA – 4020 – deadlock detected while trying to lock object”?
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: 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. Issue a TopicSession.commit call before calling createDurableSubscriber and unsubscribe call.
Related Questions
- Why do the TopicSession.createDurableSubscriber and TopicSession.unubscribe calls raise JMSException with the message "ORA - 4020 - deadlock detected while trying to lock object"?
- I just received an email message from InterScan saying, "InterScan has detected virus(es) in an incoming email attachment." What does this mean?
- When I log in to ResNet I get a message telling me an intrusion has been detected, why?
