Is It Necessary To Do Explicit Locking And Unlocking A Session (Doc ID 1364266.1)

Last updated on OCTOBER 10, 2016

Applies to:

Oracle Communications Converged Application Server - Version: 5.0.0 and later   [Release: 5.0 and later ]
Information in this document applies to any platform.

Goal

The following error is thrown from some engine tier nodes:

com.bea.wcp.sip.engine.server.UnableToLockException: Could not lock call state even after waiting for more than 5000 ms
at com.bea.wcp.sip.engine.server.CallStateManager.enter(CallStateManager.java:220)
at com.bea.wcp.sip.engine.SipSessionsUtilAdapter.getApplicationSessionById(SipSessionsUtilAdapter.java:135)
<snip>
Caused by: com.bea.wcp.sip.engine.server.LockTimeoutException: Could not lock call state 5d38aaf251074e0127c9ecbc045e6c18@IP Address even after waiting for more than 5000 ms
at com.bea.wcp.sip.engine.server.CallStateManager.doLockAndGet(CallStateManager.java:280)
at com.bea.wcp.sip.engine.server.CallStateManager.enter(CallStateManager.java:250)
at com.bea.wcp.sip.engine.server.CallStateManager.enter(CallStateManager.java:217)
... 52 more


Do we need to do explicit lock/unlocking of a session or suchlike? Or will the OCCAS container take care of all this?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms