Time Out Error When Running Action "Release Remaining Order Amount"
(Doc ID 1535975.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.1.0 to 6.2.8 [Release 6.1 to 6.2]Information in this document applies to any platform.
Symptoms
You are getting the following error on the process of OB line releasing, using the action "Release Remaining Order Amount".
RELEASE REMAINING FROM OB LINE timed out waiting for ORDER BASE LINE: DOMAIN.OBJECT_ID. The object is held by Activity: RELEASE REMAINING FROM OB LINE, Machine: DEFAULT, Thread: null, Process: 123456, Since: YYYY-MM-DD HH:MM:SS UTC.
at sun.reflect.GeneratedConstructorAccessor1395.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at glog.util.exception.GLException.factory(GLException.java:435)
at glog.util.exception.GLException.factory(GLException.java:411)
at glog.util.exception.GLException.factory(GLException.java:407)
at glog.util.exception.GLException.factory(GLException.java:395)
at glog.server.synch.object.ObjectLock.lock(ObjectLock.java:258)
at glog.server.synch.object.ObjectLock.lock(ObjectLock.java:230)
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:60)
at glog.server.wrapper.WrapperSessionBean.execDispatch(WrapperSessionBean.java:55)
at glog.server.wrapper.WrapperSessionServerSideEJBWrapper.execDispatch(WrapperSessionServerSideEJBWrapper.java:48)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.execDispatch(WrapperSessionHome_a06097_EOImpl.java:58)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
[[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)']
Changes
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 |