"NullPointerException" Exception When Using "Notify Service Provider" Action in an Agent (Doc ID 1060121.1)

Last updated on JULY 09, 2014

Applies to:

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

Symptoms


An Agent is configured to use the "Notify Service Provider" action. When this is executed on a shipment where the Service Provider uses a Contact Group, this action is failing with the following Exception:

java.lang.NullPointerException
at glog.server.workflow.notify.MailTopic.getTopicFieldValues(MailTopic.java:86)
at glog.server.workflow.Topic.getFieldValues(Topic.java:341)
at glog.comm.parameter.ParameterHolder.getArguments(ParameterHolder.java:90)
at glog.server.workflow.notify.MessageTopic.getArguments(MessageTopic.java:62)
at glog.comm.parameter.ParameterHolder.toString(ParameterHolder.java:81)
at glog.server.workflow.notify.MessageTopic.toString(MessageTopic.java:56)
at java.text.MessageFormat.subformat(MessageFormat.java:1230)
at java.text.MessageFormat.format(MessageFormat.java:825)
at java.text.Format.format(Format.java:133)
at java.text.MessageFormat.format(MessageFormat.java:801)
at glog.util.log.Log.logID(Log.java:79)
at glog.server.workflow.ServerPublisher.publish(ServerPublisher.java:66)
at glog.server.workflow.Topic.publish(Topic.java:137)
at glog.server.workflow.notify.NotifyRouter.publish(NotifyRouter.java:37)
at glog.server.workflow.notify.NotifyByEMail.publishTopic(NotifyByEMail.java:44)
at glog.server.workflow.notify.RouterWithTransformation.routeNonConsolidated(RouterWithTransformation.java:75)
at glog.server.workflow.notify.RouterWithTransformation.route(RouterWithTransformation.java:21)
at glog.server.workflow.notify.NotifyBundle.send(NotifyBundle.java:74)
at glog.server.workflow.notify.Notify.send(Notify.java:108)
at glog.server.workflow.notify.Notify.send(Notify.java:99)
at glog.server.agent.utility.AbstractNotify.execute(AbstractNotify.java:70)
at glog.server.agent.ActionWorkflow.execute(ActionWorkflow.java:51)
at glog.server.workflow.WorkflowSessionBean.execute(WorkflowSessionBean.java:64)
at glog.server.workflow.WorkflowSessionServerSideEJBWrapper.execute(WorkflowSessionServerSideEJBWrapper.java:32)
at glog.server.workflow.WorkflowSessionServerSideEJBWrapper_61kh96_EOImpl.execute(WorkflowSessionServerSideEJBWrapper_61kh96_EOImpl.java:262)
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:79)
at java.lang.Thread.run(Thread.java:534)

Note: The above description focuses on the use of a Contact Group. However this same problem would exist where the Service Provider has a single Contact.

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