My Oracle Support Banner

When Attempting to Update a Shipment Via "ShipmentActual" XML, The Following Error Is Thrown: "ShipmentActualTopic has timed out during a synchronous wait" (Doc ID 1989419.1)

Last updated on FEBRUARY 02, 2018

Applies to:

Oracle Transportation Management - Version 6.3.3 to 6.3.7 [Release 6.3]
Information in this document applies to any platform.

Symptoms

When attempting to update the shipment refnum of a shipment which is created for one ship unit of multiple ship units of the same order release
the following error occurs.



Error Exception Process ShipmentActualTopic has timed out during a synchronous wait
at sun.reflect.GeneratedConstructorAccessor915.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:460)
at glog.util.exception.GLException.factory(GLException.java:436)
at glog.util.exception.GLException.factory(GLException.java:432)
at glog.util.exception.GLException.factory(GLException.java:428)
at glog.server.workflow.OnPublishWaitTimeout.throwException(OnPublishWaitTimeout.java:55)
at glog.server.workflow.OnPublishWaitTimeout.timeout(OnPublishWaitTimeout.java:42)
at glog.server.workflow.TopicManager.publishWait(TopicManager.java:184)
at glog.server.workflow.ServerPublisher.publishWait(ServerPublisher.java:154)
at glog.server.workflow.ServerPublisher.publishWait(ServerPublisher.java:158)
at glog.server.workflow.Topic.publishWait(Topic.java:162)
at glog.business.shipmentactual.ShipmentActualExecutor.execute(ShipmentActualExecutor.java:245)
at glog.business.shipmentactual.ShipmentActualExecutor.execute(ShipmentActualExecutor.java:124)
at glog.business.shipmentactual.ShipmentActualSessionBean.executeShipmentActual(ShipmentActualSessionBean.java:99)
at glog.business.shipmentactual.ShipmentActualSessionServerSideEJBWrapper.executeShipmentActual(ShipmentActualSessionServerSideEJBWrapper.java:48)
at glog.business.shipmentactual.ShipmentActualSessionHome_4tsowh_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at glog.business.shipmentactual.ShipmentActualSessionHome_4tsowh_EOImpl.executeShipmentActual(Unknown Source)
at glog.business.shipmentactual.ShipmentPersistenceHandler.handlePersist(ShipmentPersistenceHandler.java:56)
at glog.util.persistence.PersistenceManager.execute(PersistenceManager.java:97)
at glog.server.compareengine.TopicPublisher.persist(TopicPublisher.java:161)
at glog.server.compareengine.TopicPublisher.publish(TopicPublisher.java:64)
at glog.server.compareengine.CompareEngine.compare(CompareEngine.java:116)
at glog.util.genericcontainer.GenericContainerUtilSessionBean.compare(GenericContainerUtilSessionBean.java:141)
at glog.util.genericcontainer.GenericContainerUtilSessionBean.compareAndStore(GenericContainerUtilSessionBean.java:90)
at glog.util.genericcontainer.GenericContainerUtilSessionServerSideEJBWrapper.compareAndStore(GenericContainerUtilSessionServerSideEJBWrapper.java:220)
at glog.util.genericcontainer.GenericContainerUtilSessionServerSideEJBWrapper_6hrtm7_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at glog.util.genericcontainer.GenericContainerUtilSessionServerSideEJBWrapper_6hrtm7_EOImpl.compareAndStore(Unknown Source)
at glog.integration.xmlbasewrapper.XmlBaseWrapper.persist(XmlBaseWrapper.java:288)
at glog.integration.xmlbasewrapper.XmlBaseWrapper.persistContainerSelf(XmlBaseWrapper.java:322)
at glog.integration.application.shipment.ShipmentWrapper.persistContainerSelf(ShipmentWrapper.java:1381)
at glog.integration.xmlbasewrapper.XmlBaseWrapper.persistViaContainer(XmlBaseWrapper.java:382)
at glog.integration.application.shipment.ShipmentInterface.persistIndivXML(ShipmentInterface.java:265)
at glog.integration.application.shipment.ShipmentInterface.persistXML(ShipmentInterface.java:193)
at glog.integration.application.BaseInterface.persistXMLBase(BaseInterface.java:195)
at glog.integration.application.TransactionProcessor.processTransaction(TransactionProcessor.java:223)
at glog.integration.application.TransactionProcessor.processTransaction(TransactionProcessor.java:353)
at glog.server.workflow.transproc.TransProc.execute(TransProc.java:110)
at glog.server.workflow.SimpleWorkflow.execute(SimpleWorkflow.java:23)
at glog.server.workflow.WorkflowSessionBean.execute(WorkflowSessionBean.java:64)
at glog.server.workflow.WorkflowSessionNonTransServerSideEJBWrapper.execute(WorkflowSessionNonTransServerSideEJBWrapper.java:40)
at glog.server.workflow.WorkflowSessionNonTransServerSideEJBWrapper_t6tuwu_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at glog.server.workflow.WorkflowSessionNonTransServerSideEJBWrapper_t6tuwu_EOImpl.execute(Unknown Source)
at glog.server.workflow.WorkflowManager.execute(WorkflowManager.java:356)
at glog.server.workflow.Trigger.trigger(Trigger.java:122)
at glog.util.event.MemoryEventQueueRunnable.processEvent(MemoryEventQueueRunnable.java:145)
at glog.util.event.MemoryEventQueueRunnable.run(MemoryEventQueueRunnable.java:100)
at glog.util.event.EventThread.run(EventThread.java:86)
at java.lang.Thread.run(Thread.java:680)
publishWait - 1
Process ShipmentActualTopic has timed out during a synchronous wait


The issue can be reproduced at will with the following steps:
1. Create one order release with 5 ship units
2. Planned the order release and obtained 5 shipments
3. Integrated the attached shipmentactual.xml which update the shipment refnum of one of the five above shipments
4. Review the logs after the integration happens
5. OTM loads all five ship units, which in the customer's case leads to locks.



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!


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