Posted: Tue Mar 12, 2013 9:28 pm Post subject: The SOAP Reply node 'BH_BS.BH_ECI_SAP_UpdateInstallationServ
Newbie
Joined: 28 Feb 2013 Posts: 4
Hi As per my requirement, Source system expecting Error message from WMB. I added SoapReply to my error handling subflow. So whenever gets exception that would be send back to source sys as this is webservice call.
But I am getting following error..
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>BIP3113E: Exception detected in message flow BH_BS.BH_ECI_SAP_UpdateInstallationServiceEvent.ECI_SOAP Input (broker BHBKRDV2)</faultstring>
<detail>
<Text>BIP3752E: The SOAP Reply node 'BH_BS.BH_ECI_SAP_UpdateInstallationServiceEvent.ECI_SOAP Reply' encountered an error while processing a reply message.
An error occurred during reply message processing.
See previous error messages to determine the cause of the error. : /build/S700_P/src/WebServices/WSLibrary/ImbSOAPReplyNode.cpp: 391: ImbSOAPReplyNode::evaluate: ComIbmSOAPReplyNode: BH_BS/BH_ECI_SAP_UpdateInstallationServiceEvent#FCMComposite_1_12
BIP3701E: A Java exception was thrown whilst calling the Java JNI method ''method_com_ibm_broker_axis2_Axis2Invoker_prepareToSendReplyNonSOAP''. The Java exception was ''org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x50) was found in the prolog of the document.''. The Java stack trace was ''Frame : 0 org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x50) was found in the prolog of the document.| @: org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:255)| @: org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:132)| @: org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:539)| @: com.ibm.broker.axis2.SoapUtilities.wrapDataInSoapEnvelopeIfRequiredAvoidingAxis2(SoapUtilities.java:1762)| @: com.ibm.broker.axis2.Axis2Invoker.prepareToSendReplyNonSOAP(Axis2Invoker.java:1064)|Frame : 1 javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x50) was found in the prolog of the document.| @: com.ibm.xml.xlxp2.api.stax.msg.StAXMessageProvider.throwWrappedXMLStreamException(StAXMessageProvider.java:76)| @: com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.produceFatalErrorEvent(XMLStreamReaderImpl.java:2013)| @: com.ibm.xml.xlxp2.api.jaxb.JAXBXMLStreamReader.produceFatalErrorEvent(JAXBXMLStreamReader.java:316)| @: com.ibm.xml.xlxp2.scan.DocumentScanner.reportFatalError(DocumentScanner.java:4821)| @: com.ibm.xml.xlxp2.scan.DocumentScanner.reportFatalError(DocumentScanner.java:1205)| @: com.ibm.xml.xlxp2.scan.DocumentScanner.scanProlog(DocumentScanner.java:1770)| @: com.ibm.xml.xlxp2.scan.DocumentScanner.nextEvent(DocumentScanner.java:1316)| @: com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:586)| @: com.ibm.xml.xlxp2.api.stax.XMLInputFactoryImpl$XMLStreamReaderProxyImpl.next(XMLInputFactoryImpl.java:183)| @: com.ibm.xml.xlxp2.api.wssec.WSSXMLInputFactory$WSSStreamReaderProxy.next(WSSXMLInputFactory.java:55)| @: org.apache.axiom.om.impl.builder.StAXBuilder.parserNext(StAXBuilder.java:567)| @: org.apache.axiom.om.impl.builder.StAXOMBuilder.nextToken(StAXOMBuilder.java:634)| @: org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:175)| @: org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:132)| @: org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:539)| @: com.ibm.broker.axis2.SoapUtilities.wrapDataInSoapEnvelopeIfRequiredAvoidingAxis2(SoapUtilities.java:1762)| @: com.ibm.broker.axis2.Axis2Invoker.prepareToSendReplyNonSOAP(Axis2Invoker.java:1064)''.
Correct the error, and if necessary redeploy the flow. : /build/S700_P/src/WebServices/WSLibrary/ImbSOAPReplyHelper.cpp: 433: ImbSOAPReplyHelper::makeSOAPReply: :</Text>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
What does this tell you?
Quote:
An invalid XML character (Unicode: 0x50) was found in the prolog of the document.
What does a user trace show?
Have you tried writing the reply message to a queue and examining it?
There are all manner of things you could do to help yourself investigate the problem that will probably take less time than waiting for an unofficial reply in this forum.
Please let is know what you are trying so that we can eliminate those options from any replies you receive. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum