My Oracle Support Banner

In Driver - Nat/Nal Manual Override Action Getting Timed Out (Doc ID 1087236.1)

Last updated on MAY 06, 2022

Applies to:

Oracle Transportation Management - Version 6.1.0 and later
Information in this document applies to any platform.

Symptoms

On : 6.1 version, Asset Management

When attempting to Action any selected driver in Driver manager with NAT/NAL Override, (with an agent that listens to "Driver - NAT NAL Manual Override" to send an integration) it times out ,and the following error occurs.

ERROR
-----------------------
2010-02-15 19:16:07.817 90780 Error Exception NAT/NAL MANUAL OVERRRIDE timed out waiting for DRIVER: MA.DRIVER3. The object is held by Activity: SEND INTEGRATION (AGENT), Machine: DEFAULT, Thread: lifetime - 1, Process: null, Since: 2010-02-15 19:15:07 America/New_York.

at sun.reflect.GeneratedConstructorAccessor416.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:434)
at glog.util.exception.GLException.factory(GLException.java:410)
at glog.util.exception.GLException.factory(GLException.java:406)
at glog.util.exception.GLException.factory(GLException.java:394)
at glog.server.synch.object.ObjectLock.lock(ObjectLock.java:240)
at glog.server.synch.object.ObjectLock.lock(ObjectLock.java:212)
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:53)
at glog.server.wrapper.WrapperSessionServerSideEJBWrapper.execDispatch(WrapperSessionServerSideEJBWrapper.java:48)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.execDispatch(WrapperSessionHome_a06097_EOImpl.java:61)
at glog.server.wrapper.WrapperSessionHome_a06097_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(SecurityManager.java:147)
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)
[



STEPS
-----------------------
The issue can be reproduced at will with the following steps:


1. Create an agent with similar to the following:
Business Process Automation -> Agent and Milestones -> Automation Agent
Ensure that there is a Agent with
Agent Type = Driver
Event = Driver - NAT/NAL MANUAL OVERRIDE
In Actions Tab,
Action = SEND INTEGRATION
with Notify Method = Queue
External SyStem with
XML Element ID = Driver
and OUTXML Profile ID with default Mode =MAX

2. Create Drivers

3. Navigate to Fleet Management >Driver Management> Driver Manager

4. Click on search

5. Select any driver

6. Click on Actions tab, expand Fleet Management, Driver Position, then click on action "NAT/NAL Override"

7. System hangs with the following error thrown after a while:

At 2010-02-16 22:48:57.871
NAT/NAL MANUAL OVERRRIDE timed out waiting for DRIVER: MA.DRIVER5. The object is held by Activity: SEND INTEGRATION (AGENT), Machine: DEFAULT, Thread: lifetime - 1, Process: null, Since: 2010-02-16 22:47:57 America/New_York.

at sun.reflect.GeneratedConstructorAccessor416.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:434)
at glog.util.exception.GLException.factory(GLException.java:410)
at glog.util.exception.GLException.factory(GLException.java:406)
at glog.util.exception.GLException.factory(GLException.java:394)
at glog.server.synch.object.ObjectLock.lock(ObjectLock.java:240)
at glog.server.synch.object.ObjectLock.lock(ObjectLock.java:212)
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:53)
at glog.server.wrapper.WrapperSessionServerSideEJBWrapper.execDispatch(WrapperSessionServerSideEJBWrapper.java:48)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.execDispatch(WrapperSessionHome_a06097_EOImpl.java:61)
at glog.server.wrapper.WrapperSessionHome_a06097_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(SecurityManager.java:147)
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)
8. Inactivate the agent, go through the same steps above, selec radio-button Manual, enter “Next Available Time”, “Next Available Location”, and click Finish button, gets the following:
Confirmation
Success
The next available location and the next available time of the driver has been set




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