Object Lock Timeout Errors Received When Attempting To Edit A Shipment in Scalability Environment (Doc ID 1320102.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Transportation Management - Version 5.5.05.07 to 6.2.4 [Release 5.5 to 6.2]
Information in this document applies to any platform.
***Checked for relevance on 08-Oct-2012***

Symptoms


The following error is receive dwhen attempting to edit a shipment even though the lock does not show the Object Lock Servlet.

Error:

2011-04-26 13:48:40.791 358078 Error Exception CHANGE STOP TIME timed out waiting for {dataQueryType=null}: {objectGid=null} (lockObjectId=SLS.11042201442, lockType=SHIPMENT)

at sun.reflect.GeneratedConstructorAccessor414.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at glog.util.exception.GLException.factory(GLException.java:413)
at glog.util.exception.GLException.factory(GLException.java:390)
at glog.util.exception.GLException.factory(GLException.java:386)
at glog.server.synch.object.ObjectLock.lock(ObjectLock.java:229)
at glog.server.synch.object.ObjectLock.lock(ObjectLock.java:207)
at glog.server.synch.object.ObjectLocks$1.lock(ObjectLocks.java:85)
at glog.server.synch.object.ObjectLocks$MultiLock.retrieve(ObjectLocks.java:165)
at glog.server.synch.object.ObjectLocks.lock(ObjectLocks.java:88)
at glog.server.synch.object.ObjectLocks.lock(ObjectLocks.java:65)
at glog.server.synch.object.ObjectLocks.lock(ObjectLocks.java:53)
at glog.server.wrapper.WrapperEventInfo.getLocks(WrapperEventInfo.java:64)
at glog.server.wrapper.WrapperSessionBean.execDispatch(WrapperSessionBean.java:52)
at glog.server.wrapper.WrapperSessionServerSideEJBWrapper.execDispatch(WrapperSessionServerSideEJBWrapper.java:42)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.execDispatch(WrapperSessionHome_a06097_EOImpl.java:46)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Must be a SCA environment
2. Modify a shipment through the UI
3. Wait a minute
4. Run "Object Lock Cleanup" process on objects older than 1 minute
5. Attempt to modify the same shipment and note the error received:
Exception CHANGE STOP TIME timed out waiting for {dataQueryType=null}: {objectGid=null} (lockObjectId=SLS.11042201442, lockType=SHIPMENT).
6. The error usually continues for the same object until the application is restart.

Cause

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