Java.Lang.NullPointerException Error When Sending Transmission Report to Legacy Servlet URL (Doc ID 437325.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

If an XML file is configured to send out an outbound transmission report to a URL provided in the ServletURL element, the report is not sent and the following error is seen in the log:

Error Exception java.lang.NullPointerException

java.lang.NullPointerException
at
glog.util.httppost.HttpPostEvent$Listener.doPost(HttpPostEvent.java:303)
at
glog.util.httppost.HttpPostEvent$Listener.trigger(HttpPostEvent.java:226)
at
glog.util.event.MemoryEventQueueRunnable.processEvent(MemoryEventQueueRunnable
.java(Compiled
Code))
at
glog.util.event.MemoryEventQueueRunnable.run(MemoryEventQueueRunnable.java:96)
.
at glog.util.event.EventThread.run(EventThread.java:79)
at
com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:254)
at java.security.AccessController.doPrivileged1(Native Method)
at
java.security.AccessController.doPrivileged(AccessController.java(Compiled
Code))
at javax.security.auth.Subject.doAs(Subject.java:477)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:118)
at
com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java:325)
at java.security.AccessController.doPrivileged1(Native Method)
at
java.security.AccessController.doPrivileged(AccessController.java(Compiled
Code))
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:1027)
at
com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContex
tImpl.java:195)
at com.ibm.ws.asynchbeans.CJWorkItemImpl.run(CJWorkItemImpl.java:187)
at java.lang.Thread.run(Thread.java:570)
[transport - HTTP - 1]

To Replicate:

Under the TransmissionHeader of an XML file (for example: location):
- Check the AckOption=YES in the XML
- Set the ServletURL value to an appropriate URL where you can receive the transmission report XML.
- Set the ComMethodGid/Xid=HTTPPOST in the XML.
- Upload the transmission to OTM.
- You will not receive the transmission report and find the above mentioned error in the glog.app.log file. 

Cause

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