BPEL 10.1.3.5: WSIFOperation returns error "Start of root element expected"

Question

We have a customer reporting that one of the integration flow from EBS to OTM errors out with the above error. The flow works most of the time fine. But in some cases it errors out, with the error , however, there is no log in ithe OTM , for this , only the oc4j log has the following.
It is not clear, if the BPEL errored out on the bad response from the OTM server or the BPEL failed to invoke the OTM servlet. How to determine the what is causing the issue?
<2010-11-02 09:52:24,863> <DEBUG> <EbsCRP3domain.collaxa.cube.ws> <WSIFInvocationHandler::invoke> invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: [email protected] : Could not invoke 'process'; nested exception is:
     oracle.xml.parser.v2.XMLParseException: Start of root element expected.
     at com.collaxa.cube.ws.wsif.providers.http.WSIFOperation_HTTP.executeRequestResponseOperation(WSIFOperation_HTTP.java:501)
     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:480)
     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:529)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:266)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:828)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:411)
     at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:200)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:4174)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1680)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
     at com
The OTM integration thread http://myforums.oracle.com/jive3/thread.jspa?messageID=5042541 has the complete log file from oc4j
Also the customer bug: 10247951
Edited by: user519303 on Nov 4, 2010 8:04 PM

Answer 1

The content has the delivery informatiuon for the orders. The content differs for the errored ones, in the sense that it is for different delivery. The namespace etc are the same. There are about hundred GLogXMLElement in the payload.
<Transmission xmlns:ns1="http://xmlns.oracle.com/apps/otm" xmlns="http://xmlns.oracle.com/apps/otm">
<ns1:TransmissionHeader>
<ns1:UserName>STI.ADMIN</ns1:UserName>
<ns1:Password>CHANGEME</ns1:Password>
</ns1:TransmissionHeader>
<ns1:TransmissionBody>
<ns1:GLogXMLElement>
<ns1:TransactionCode>IU</ns1:TransactionCode>
<ns1:LocationGid>
<ns1:Gid>
<ns1:DomainName>STI</ns1:DomainName>
<ns1:Xid>CUS-11726</ns1:Xid>
</ns1:Gid>
</ns1:LocationGid>
<ns1:LocationName>Starbucks Fresh - Dallas</ns1:LocationName>
<ns1:Address>
<ns1:CountryCode3Gid>
<ns1:Gid>
<ns1:DomainName>PUBLIC</ns1:DomainName>
<ns1:Xid>USA</ns1:Xid>
</ns1:Gid>
</ns1:CountryCode3Gid>
</ns1:Address>
<ns1:LocationRefnum>
<ns1:LocationRefnumQualifierGid>
<ns1:Gid>
<ns1:DomainName>PUBLIC</ns1:DomainName>
<ns1:Xid>ORIGIN</ns1:Xid>
</ns1:Gid>
</ns1:LocationRefnumQualifierGid>
<ns1:LocationRefnumValue>CUSTOMER</ns1:LocationRefnumValue>
</ns1:LocationRefnum>
<ns1:LocationRefnum>
<ns1:LocationRefnumQualifierGid>
<ns1:Gid>
<ns1:DomainName>PUBLIC</ns1:DomainName>
<ns1:Xid>CUSID</ns1:Xid>
</ns1:Gid>
</ns1:LocationRefnumQualifierGid>
<ns1:LocationRefnumValue>S58551</ns1:LocationRefnumValue>
</ns1:LocationRefnum>
<ns1:LocationRefnum>
<ns1:LocationRefnumQualifierGid>
<ns1:Gid>
<ns1:DomainName>PUBLIC</ns1:DomainName>
<ns1:Xid>CUSNM</ns1:Xid>
</ns1:Gid>
</ns1:LocationRefnumQualifierGid>
<ns1:LocationRefnumValue>Starbucks Fresh - Dallas</ns1:LocationRefnumValue>
</ns1:LocationRefnum>
<ns1:LocationRole>
<ns1:LocationRoleGid>
<ns1:Gid>
<ns1:DomainName>PUBLIC</ns1:DomainName>
<ns1:Xid>CUSTOMER</ns1:Xid>
</ns1:Gid>
</ns1:LocationRoleGid>
</ns1:LocationRole>
<ns1:Corporation>
<ns1:CorporationName>Starbucks Fresh - Dallas</ns1:CorporationName>
</ns1:Corporation>
</ns1:Location>
</ns1:GLogXMLElement>
</ns1:TransmissionBody>
</Transmission>