My Oracle Support Banner

"Shipment graph has zero or more than one root shipment node." When Running Agent Action "ORDER RELEASE - MOD - EDIT SHIPMENT" (Doc ID 1107333.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version: 5.5 and later   [Release: 5.5 and later ]
Information in this document applies to any platform.

Symptoms


If the service time flag is checked on the agent action ORDER RELEASE - MOD - EDIT SHIPMENT and the order is split across multiple shipment due to size of order, the result is that the agent fails and the shipment/order are left in a corrupt state.

Exception Shipment graph has zero or more than one root shipment node.

at sun.reflect.GeneratedConstructorAccessor220.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at glog.util.exception.GLException.factory(GLException.java:413)
at glog.util.exception.GLException.factory(GLException.java:390)
at glog.business.rate.rateservice.RateServiceSession.calculateRateServiceResultWindows(RateServiceSession.java:895)
at glog.business.action.omd.OMDProcessor.editShipmentsForOrderRelease(OMDProcessor.java:541)
at glog.business.session.OMDProcessorSessionBean.editShipmentsForOrderRelease(OMDProcessorSessionBean.java:105)
at glog.business.session.OMDProcessorSessionServerSideEJBWrapper.editShipmentsForOrderRelease(OMDProcessorSessionServerSideEJBWrapper.java:112)
at glog.business.session.OMDProcessorSessionHome_f09cq7_EOImpl.editShipmentsForOrderRelease(OMDProcessorSessionHome_f09cq7_EOImpl.java:586)
at glog.server.agent.business.order.ORModEditShipment.process(ORModEditShipment.java:86)
at glog.server.agent.business.order.ORActionTopic.persist(ORActionTopic.java:47)
at glog.server.agent.PersistActionTopic.execute(PersistActionTopic.java:34)
at glog.server.agent.ActionWorkflow.execute(ActionWorkflow.java:51)
at glog.server.workflow.WorkflowSessionBean.execute(WorkflowSessionBean.java:64)
at glog.server.workflow.WorkflowSessionNonTransServerSideEJBWrapper_t6tuwu_EOImpl.execute(WorkflowSessionNonTransServerSideEJBWrapper_t6tuwu_EOImpl.java:100)
at glog.server.workflow.WorkflowManager.execute(WorkflowManager.java:341)
at glog.server.workflow.Trigger.trigger(Trigger.java:123)
at glog.util.event.MemoryEventQueueRunnable.processEvent(MemoryEventQueueRunnable.java:141)
at glog.util.event.MemoryEventQueueRunnable.run(MemoryEventQueueRunnable.java:96)
at glog.util.event.EventThread.run(EventThread.java:82)
at java.lang.Thread.run(Thread.java:534)

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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

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