Webservices do not Work After Applying CU6 (Doc ID 977602.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version: 5.5.06 to 5.5.06 - Release: 5.5 to 5.5
Information in this document applies to any platform.
***Checked for relevance on 07-Jul-2011***

Symptoms

After Upgrading to CU6 Release of OTM Version 5.5, Using Webservices to send XML messages to OTM, BPEL sends the message to OTM, after considerable delay an error message is sent back to BPEL.

ERROR
-----------------------

The error message for the outbound message:

IMessageText = CAUGHT THE FOLLOWING EXCEPTION WHILE PROCESSING TRANSMISSION OUTBOUND: OTM failed to send SERVICE transmission 368,957 from Instance name.domain name to ServiceName OTMSoap, operation process, url http://domain:port /orabpel/default/OTMSoap/OTMSoap?wsdl with the following Exception: java.lang.NullPointerException java.lang.NullPointerException at weblogic.xml.xmlnode.XMLNode.createStartElement(XMLNode.java:772) at weblogic.xml.xmlnode.XMLNode.write(XMLNode.java:653) at weblogic.webservice.core.encoding.stream.SOAPElementCodec.serialize(SOAPElementCodec.java:79) at weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec.serialize(XSDAnyCodec.java:75) at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:188) at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:174) at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:328) at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:297) at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:645) at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:206) at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143) at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:471) at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457) at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:566) at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:419) at glog.util.j2ee.webservice.ASWebServiceHelper.invokeCall(ASWebServiceHelper.java:79) at glog.server.webservice.WebServiceCall.call(WebServiceCall.java:176) at glog.server.webservice.WebServiceCall.call(WebServiceCall.java:107) at glog.server.workflow.webservice.ServiceTransmission.execute(ServiceTransmission.java:99) at glog.server.workflow.webservice.ServiceCall.executeWithReturn(ServiceCall.java:31) at glog.server.workflow.webservice.ServiceCallTopic.execute(ServiceCallTopic.java:19) at glog.server.workflow.SimpleWorkflow.execute(SimpleWorkflow.java:23) 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)
TimeStamp = 20091015102339
DomainName = xxxxx



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. On OTM Version 5.5.06, Send an XML interface into OTM using web Services
2. See the Error message in BPEL after a while




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