My Oracle Support Banner

javax.ejb.EJBException: [EJB:010108]The EJB Lock Manager has received an unlock request from EJB! (Doc ID 1169897.1)

Last updated on APRIL 13, 2018

Applies to:

Oracle Weblogic Server - Version 9.2 to 10.3
Information in this document applies to any platform.

Symptoms

When making calls to EJB's from client code, we get a warning message saying "The EJB Lock Manager has received an unlock request from EJB:SystemTask with primary key".

javax.ejb.EJBException: [EJB:010108]The EJB Lock Manager has received an unlock request from EJB:sims.ejb.GridSetupLEB with primary key:CT.


However, this primary key can't be found in the Lock Manager. This indicates either an EJB container bug, or the 'equals' and 'hashCode' methods for the primary key class:com.sims.ejb.user.UserPK are implemented incorrectly.

Please check the 'equals' and 'hashCode' implementations.

at weblogic.ejb.container.locks.ExclusiveLockManager$LockBucket.unlock(ExclusiveLockManager.java:409)
at weblogic.ejb.container.locks.ExclusiveLockManager.unlock(ExclusiveLockManager.java:170)
at weblogic.ejb.container.manager.ExclusiveEntityManager.afterCompletion(ExclusiveEntityManager.java:726)
at weblogic.ejb.container.manager.ExclusiveEntityManager.afterCompletion(ExclusiveEntityManager.java:670)
at weblogic.ejb.container.internal.TxManager$TxListener.afterCompletion(TxManager.java:984)

Cause

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
Symptoms
Changes
Cause
Solution
References


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