"Generic Remote Exception" is Generated When a Charter Voyage Vessel ID and/or the Arrival/Departure Dates are Modified (Doc ID 1463054.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

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

Symptoms

When charter voyage vessel id and/or the arrival/departure dates are modified, the following error occurs.

ERROR
-----------------------
Generic_Remote_Exception

weblogic.ejb20.locks.LockTimedOutException: [EJB:010107]The lock request from EJB:ejb.CharterVoyage with primary key:UPM.94894 timed-out after waiting 300,000 ms. The transaction or thread requesting the lock was:Name=[EJB glog.server.xmlupdate.XMLUpdateSessionServerSideEJBWrapper.updateAndTrack(glog.webserver.util.XMLContainer,java.lang.String,java.lang.String,glog.webserver.umt.UserPreference,glog.server.wrapper.WrapperEventInfo,glog.util.persistence.PersistenceHandler)],Xid=BEA1-3AEFDF14F7F86A77A607(1365692524),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=300,seconds left=6900,activeThread=Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=started,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@5166d0ca,re-Registered = false),SCInfo[Otmv620+gc3-fikylx54]=(state=active),properties=({weblogic.transaction.name=[EJB glog.server.xmlupdate.XMLUpdateSessionServerSideEJBWrapper.updateAndTrack(glog.webserver.util.XMLContainer,java.lang.String,java.lang.String,glog.webserver.umt.UserPreference,glog.server.wrapper.WrapperEventInfo,glog.util.persistence.PersistenceHandler)], ISOLATION LEVEL=2, weblogic.jdbc=t3://141.172.68.238:7001=null}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=gc3-fikylx54+141.172.68.238:7001+Otmv620+t3+, XAResources={WLStore_Otmv620__WLS_gc3-fikylx54, WSATGatewayRM_gc3-fikylx54_Otmv620, weblogic.jdbc.wrapper.JTSXAResourceImpl=null},NonXAResources={=null})],CoordinatorURL=gc3-fikylx54+141.172.68.238:7001+Otmv620+t3+).

REPLICATION STEPS
-----------------------
This issue can occur when working with a large number of orders, 100 or more, where some orders may split across multiple console shipments.

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