My Oracle Support Banner

NullPointerException On Match Shipment Using Saved Query No Stop Number (Doc ID 1605555.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Transportation Management - Version 6.1.0 to 6.3.4 [Release 6.1 to 6.3]
Information in this document applies to any platform.


A Tracking Event agent is configured with a Match Shipment action using Saved Query. If the Tracking Event does not have a Stop Number, the action fails with the following exception. If a stop number is included on the Tracking Event, it is successful.

at glog.ejb.shipment.db.ShipmentStopPK.hashCode(
at java.util.HashMap.put(
at java.util.HashSet.add(
at java.util.AbstractCollection.addAll(
at java.util.HashSet.(
at glog.server.agent.ActionWorkflow.execute(
at glog.server.workflow.WorkflowSessionBean.execute(
at glog.server.workflow.WorkflowSessionServerSideEJBWrapper.execute(
at glog.server.workflow.WorkflowSessionServerSideEJBWrapper_61kh96_EOImpl.execute(
at glog.server.workflow.WorkflowManager.execute(
at glog.server.workflow.Trigger.trigger(
at glog.util.event.MemoryEventQueueRunnable.processEvent(


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.