My Oracle Support Banner

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

Last updated on JUNE 06, 2019

Applies to:

Oracle Communications Converged Application Server - Version 5.0.0 and later
Information in this document applies to any platform.


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(
at com.bea.wcp.sip.engine.SipSessionsUtilAdapter.getApplicationSessionById(
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(
at com.bea.wcp.sip.engine.server.CallStateManager.enter(
at com.bea.wcp.sip.engine.server.CallStateManager.enter(
... 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?


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.