My Oracle Support Banner

Shipment Actuals Cost Update Via Integration Is Failing With "Generic_Remote_Exception" When The XML Contains An Accessorial That Does Not Exist In OTM. (Doc ID 1455766.1)

Last updated on MAY 06, 2022

Applies to:

Oracle Transportation Management - Version 6.2.5 to 6.2.6 [Release 6.2]
Information in this document applies to any platform.


On OTM version 6.2.5

When attempting to upload a Shipment Actual update where the accessorial code listed does not exist in OTM the following error is seen in the logs:

Error Exception Generic_Remote_Exception
  weblogic.ejb20.locks.LockTimedOutException: [EJB:010107]The lock request from EJB:ejb.Shipment with primary key:TMS.20120213-S-00005 timed-out after waiting 300,000 ms. The transaction or thread requesting the lock was:Name=[EJB glog.server.workflow.WorkflowSessionServerSideEJBWrapper.execute(glog.server.workflow.WorkflowFactory,glog.server.workflow.Trigger,glog.server.workflow.Topic)],Xid=BEA1-42C19017EB9330FD6028(622352114),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=300,seconds left=6899,activeThread=Thread[execution - 1,5,Pooled Threads],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=started,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@2518c985,re-Registered = false),SCInfo[Otmv620+gc3-usgcdmz0110]=(state=active),properties=({[EJB

The issue can be reproduced at will with the following steps:
1. Attempt to upload an Actual Shipment XML, where the XML references an Accessorial that does not exist in OTM.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.