My Oracle Support Banner

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 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***


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


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(
at java.lang.reflect.Constructor.newInstance(
at glog.util.exception.GLException.factory(
at glog.util.exception.GLException.factory(
at glog.util.exception.GLException.factory(
at glog.server.synch.object.ObjectLock.lock(
at glog.server.synch.object.ObjectLock.lock(
at glog.server.synch.object.ObjectLocks$1.lock(
at glog.server.synch.object.ObjectLocks$MultiLock.retrieve(
at glog.server.synch.object.ObjectLocks.lock(
at glog.server.synch.object.ObjectLocks.lock(
at glog.server.synch.object.ObjectLocks.lock(
at glog.server.wrapper.WrapperEventInfo.getLocks(
at glog.server.wrapper.WrapperSessionBean.execDispatch(
at glog.server.wrapper.WrapperSessionServerSideEJBWrapper.execDispatch(
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.execDispatch(
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(
at weblogic.rmi.internal.BasicServerRef$
at weblogic.rmi.internal.BasicServerRef.handleRequest(
at weblogic.rmi.internal.BasicExecuteRequest.execute(
at weblogic.kernel.ExecuteThread.execute(

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.


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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.