MQSeries.net :: View topic - SoapRequest node exception

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SoapRequest node exception

SoapRequest node exception

« View previous topic :: View next topic »

Author

Message

napier

Posted: Thu Nov 04, 2010 6:14 am Post subject: SoapRequest node exception

Apprentice

Joined: 09 Oct 2007
Posts: 48
Location: USA

We use SOAPRequest node to call an external webservice. The flow configured as a 2 way ssl communication and soap signing. The flow intermittently throws following exception when calling the webservice.

Quote:

A Java exception was thrown whilst calling the Java JNI method 'Axis2Requester_processResponseMessageSync'. The Java exception was 'org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: White space is required between "SYSTEM" and the system identifier.'. The Java stack trace was 'Frame : 0 org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: White space is required between "SYSTEM" and the system identifier.| @: org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:254)| @: org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:156)| @: org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init>(StAXSOAPModelBuilder.java:105)| @: com.ibm.broker.axis2.SoapUtilities.createSOAPMessage(SoapUtilities.java:2149)| @: com.ibm.broker.axis2.SoapUtilities.createSOAPMessage(SoapUtilities.java:1853)| @: com.ibm.broker.axis2.Axis2Requester.processResponseMessageSync(Axis2Requester.java:1342)|Frame : 1 javax.xml.stream.XMLStreamException: White space is required between "SYSTEM" and the system identifier.| @: com.ibm.xml.xlxp2.api.stax.msg.StAXMessageProvider.throwWrappedXMLStreamException(StAXMessageProvider.java:76)| @: com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.produceFatalErrorEvent(XMLStreamReaderImpl.java:2006)| @: com.ibm.xml.xlxp2.api.jaxb.JAXBXMLStreamReader.produceFatalErrorEvent(JAXBXMLStreamReader.java:316)| @: com.ibm.xml.xlxp2.scan.DocumentScanner.reportFatalError(DocumentScanner.java:4942)| @: com.ibm.xml.xlxp2.scan.DTDScanner.reportFatalError(DTDScanner.java:444)| @: com.ibm.xml.xlxp2.scan.DTDScanner.scanDoctypeDeclCommon(DTDScanner.java:534)| @: com.ibm.xml.xlxp2.api.stax.StAXDTDScanner.scanDoctypeDeclCommon(StAXDTDScanner.java:155)| @: com.ibm.xml.xlxp2.scan.DTDScanner.scanDoctypeDecl(DTDScanner.java:481)| @: com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl$DTDSupportProxy.scanDoctypeDecl(XMLStreamReaderImpl.java:227

From the exception description we were not understanding whether this exception thrown before calling the webservice or during the validation of response.
Does anyone have any idea..

kartheek.sp

Posted: Thu Apr 07, 2011 5:05 am Post subject: Facing the same issue when invoking webservice using httpreq

Novice

Joined: 05 Apr 2011
Posts: 21
Location: Pune

Facing the same issue when invoking a webservice using httprequest node.Need know it is occuring while invoking the request or after invoking it and in Response we are getting exception.

Can anybody help me out...

WMB_DEV

Posted: Wed Aug 17, 2011 11:03 am Post subject: Re: Facing the same issue when invoking webservice using htt

Novice

Joined: 23 Mar 2010
Posts: 10

kartheek.sp wrote:

Im getting the same issue while working with SOAPrequest node...
Any information on how to troubleshoot this?

mqjeff

Posted: Wed Aug 17, 2011 11:07 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Take a service trace of the flow and open a PMR.

lancelotlinc

Posted: Thu Aug 18, 2011 4:25 am Post subject:

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Nice use of [c o d e] tags, thanks. Please tell us what version you using. While you are waiting on the PMR, turn off validation entirely and see what happens. I dont know too many implementations that faithfully adhere to the WSDL contract with regard to validations. Since it happens intermittently, probably some data coming back is causing the problem. "'Axis2Requester_processResponseMessageSync" indicates to me that it is a response issue. XMLStream reader and SAX data indicates it is a parsing issue. Turn off validation and my guess is your errors will disappear.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SoapRequest node exception

Jump to:

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

Protected by Anti-Spam ACP