javax.ejb.EJBException

[EJB:010108]The EJB Lock Manager has received an unlock request from EJB:User with primary key:administrator. However, this primary key could not 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.armanta.ejb.user.UserPK are implemented incorrectly. Please check the equals and hashCode implementations.

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web3

  • via Unknown by 553756,
  • Stack trace

    • javax.ejb.EJBException: [EJB:010108]The EJB Lock Manager has received an unlock request from EJB:User with primary key:administrator. However, this primary key could not 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.armanta.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:995) at weblogic.transaction.internal.ServerSCInfo.doAfterCompletion(ServerSCInfo.java:1032) at weblogic.transaction.internal.ServerSCInfo.callAfterCompletions(ServerSCInfo.java:1011) at weblogic.transaction.internal.ServerTransactionImpl.callAfterCompletions(ServerTransactionImpl.java:2990) at weblogic.transaction.internal.ServerTransactionImpl.afterCommittedStateHousekeeping(ServerTransactionImpl.java:2890) at weblogic.transaction.internal.ServerTransactionImpl.setCommitted(ServerTransactionImpl.java:2935) at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2725) at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2645) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:282) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:230) at weblogic.ejb.container.internal.BaseEJBHome.postHomeInvoke(BaseEJBHome.java:400) at weblogic.ejb.container.internal.EntityEJBHome.findByPrimaryKey(EntityEJBHome.java:422) at com.armanta.ejb.user.User_eecm3e_HomeImpl.findByPrimaryKey(User_eecm3e_HomeImpl.java:124) at com.armanta.ejb.accesscontrol.AccessControllerBean.validateUser(AccessControllerBean.java:670) at com.armanta.ejb.accesscontrol.AccessControllerBean.getAllAuthorizationForUser(AccessControllerBean.java:111) at com.armanta.ejb.accesscontrol.AccessControllerBean.getAllAuthorizationForUser_ba(AccessControllerBean.java:152) at com.armanta.ejb.accesscontrol.AccessController_fpuyq8_EOImpl.getAllAuthorizationForUser_ba(AccessController_fpuyq8_EOImpl.java:221) at com.armanta.ejb.accesscontrol.AccessController_fpuyq8_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.