NullPointerException On Match Shipment Using Saved Query No Stop Number
(Doc ID 1605555.1)
Last updated on JULY 20, 2024
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.
Symptoms
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.
java.lang.NullPointerException
at glog.ejb.shipment.db.ShipmentStopPK.hashCode(ShipmentStopPK.java:45)
at java.util.HashMap.put(HashMap.java:450)
at java.util.HashSet.add(HashSet.java:200)
at java.util.AbstractCollection.addAll(AbstractCollection.java:305)
at java.util.HashSet.(HashSet.java:100)
at glog.server.agent.business.trackingevent.AssetMatchActionTopic.execute(AssetMatchActionTopic.java:54)
at glog.server.agent.ActionWorkflow.execute(ActionWorkflow.java:49)
at glog.server.workflow.WorkflowSessionBean.execute(WorkflowSessionBean.java:64)
at glog.server.workflow.WorkflowSessionServerSideEJBWrapper.execute(WorkflowSessionServerSideEJBWrapper.java:38)
at glog.server.workflow.WorkflowSessionServerSideEJBWrapper_61kh96_EOImpl.execute(WorkflowSessionServerSideEJBWrapper_61kh96_EOImpl.java:353)
at glog.server.workflow.WorkflowManager.execute(WorkflowManager.java:353)
at glog.server.workflow.Trigger.trigger(Trigger.java:122)
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:87)
at java.lang.Thread.run(Thread.java:619)
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 |
| References |