ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAPREQUEST NODE ERROR

Post new topic  Reply to topic
 SOAPREQUEST NODE ERROR « View previous topic :: View next topic » 
Author Message
sandip_gaikwad
PostPosted: Mon Dec 19, 2011 9:32 pm    Post subject: SOAPREQUEST NODE ERROR Reply with quote

Voyager

Joined: 25 Jul 2011
Posts: 95
I have created a sms flow where i m sending and sms through SoapRequest
The flow is as under

SOAPINPUT ->SOAPENVELOPE(developed by wsdl) -> COMPUTE NODE -> SOAP REQUEST NODE

when i am initializing the flow using SOAPUI the flow I am getting the response as sms but the flow is showing error

RecoverableException
File:CHARACTER:F:\build\S700_P\src\DataFlowEngine\TemplateNodes\ImbRequestTemplateNode.cpp
Line:INTEGER:531
Function:CHARACTER:ImbRequestTemplateNode::processMessageAssemblyToFailure
Type:CHARACTER:ImbRequestTemplateNode
Name:CHARACTER:SMSSOAP_MF#FCMComposite_1_14
Label:CHARACTER:SMSSOAP_MF.SOAP Request1
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
RecoverableException
File:CHARACTER:F:\build\S700_P\src\WebServices\WSLibrary\ImbSOAPRequestNode.cpp
Line:INTEGER:810
Function:CHARACTER:ImbSOAPRequestNode::requestData
Type:CHARACTER:ImbRequestTemplateNode
Name:CHARACTER:SMSSOAP_MF#FCMComposite_1_14
Label:CHARACTER:SMSSOAP_MF.SOAP Request1
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3754
Text:CHARACTER:Error occurred in ImbSOAPRequestHelper::makeSOAPRequest()
RecoverableException
File:CHARACTER:F:\build\S700_P\src\WebServices\WSLibrary\ImbSOAPRequestHelper.cpp
Line:INTEGER:3150
Function:CHARACTER:ImbSOAPRequestHelper::logWebServiceInvocationException
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3162
Text:CHARACTER:WebService Request Exception
Insert
Type:INTEGER:12
Text:CHARACTER:436f6e74656e742d4c656e6774683a203136320d0a436f6e74656e742d547970653a20746578742f786d6c3b20636861727365743d7574662d380d0a486f73743a206170692e6d566161796f6f2e636f6d0d0a534f4150416374696f6e3a2022220d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a0d0a
Insert
Type:INTEGER:12
Text:CHARACTER:3c3f786d6c2076657273696f6e3d22312e302220656e636f64696e673d227574662d38223f3e3c736f6170656e763a456e76656c6f706520786d6c6e733a736f6170656e763d22687474703a2f2f736368656d61732e786d6c736f61702e6f72672f736f61702f656e76656c6f70652f223e3c736f6170656e763a426f64793e3c2f736f6170656e763a426f64793e3c2f736f6170656e763a456e76656c6f70653e
Insert
Type:INTEGER:12
Text:CHARACTER:485454502f312e3020323030204f4b0d0a5365727665723a204170616368652d436f796f74652f312e310d0a436f6e74656e742d547970653a20746578742f68746d6c3b636861727365743d5554462d380d0a436f6e74656e742d4c656e6774683a2033310d0a446174653a205475652c2032302044656320323031312030353a32353a353820474d540d0a436f6e6e656374696f6e3a20636c6f73650d0a0d0a
Insert
Type:INTEGER:12
Text:CHARACTER:5374617475733d302c696e7333375f31333234333538373538393539360d0a
Insert
Type:INTEGER:5
Text:CHARACTER:POST /mvaayooapi/MessageCompose?user=nitinwaradkar@yahoo.in:25april89&senderID=TEST%20SMS&receipientno=8983275437&dcs=0&msgtxt=sweet%20little%20poeam&state=4 HTTP/1.1

RecoverableException
File:CHARACTER:F:\build\S700_P\src\WebServices\WSLibrary\ImbSOAPRequestHelper.cpp
Line:INTEGER:1832
Function:CHARACTER:ImbSOAPRequestHelper::makeSOAPRequest
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3701
Text:CHARACTER:Error Making SOAP JNI Call: Axis2Requester_processResponseMessageSync
Insert
Type:INTEGER:5
Text:CHARACTER:Axis2Requester_processResponseMessageSync
Insert
Type:INTEGER:5
Text:CHARACTER:org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x53) was found in the prolog of the document.
Insert
Type:INTEGER:5
Text:CHARACTER:Frame : 0 org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x53) was found in the prolog of the document.
@: 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:2169)
@: com.ibm.broker.axis2.SoapUtilities.createSOAPMessage(SoapUtilities.java:1873)
@: com.ibm.broker.axis2.Axis2Requester.processResponseMessageSync(Axis2Requester.java:1451)
@: com.ibm.broker.plugin.MbRoute._propagate(Native Method)
@: com.ibm.broker.plugin.MbRoute.propagate(MbRoute.java:87)
@: com.ibm.broker.soap.SoapExtractNode.routeToOperationLabelNode(SoapExtractNode.java:386)
@: com.ibm.broker.soap.SoapExtractNode.evaluate(SoapExtractNode.java:176)
@: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1469)
Frame : 1 javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x53) 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: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.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:579)
@: 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.StAXOMBuilder.parserNext(StAXOMBuilder.java:632)
@: org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:174)
@: 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:2169)
@: com.ibm.broker.axis2.SoapUtilities.createSOAPMessage(SoapUtilities.java:1873)
@: com.ibm.broker.axis2.Axis2Requester.processResponseMessageSync(Axis2Requester.java:1451)
@: com.ibm.broker.plugin.MbRoute._propagate(Native Method)
@: com.ibm.broker.plugin.MbRoute.propagate(MbRoute.java:87)
@: com.ibm.broker.soap.SoapExtractNode.routeToOperationLabelNode(SoapExtractNode.java:386)
@: com.ibm.broker.soap.SoapExtractNode.evaluate(SoapExtractNode.java:176)
@: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1469)

kindly help in resolving the issue
Back to top
View user's profile Send private message
marko.pitkanen
PostPosted: Mon Dec 19, 2011 11:15 pm    Post subject: Reply with quote

Chevalier

Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
Hi,

Your answer hides in hex dumps inside the exception. Convert them to ascii and you can see why node can't parse response with XMLNSC -parser. 2 first are request header and the request and next are response header and response.


--
Marko
Back to top
View user's profile Send private message Visit poster's website
sandip_gaikwad
PostPosted: Tue Dec 20, 2011 12:01 am    Post subject: SOAPREQUEST NODE ERROR Reply with quote

Voyager

Joined: 25 Jul 2011
Posts: 95
Thanks for the reply

But how can i convert XML into ascii using compute node
and should i have to add SOAPREPLY Node also in the end
Back to top
View user's profile Send private message
marko.pitkanen
PostPosted: Tue Dec 20, 2011 12:32 am    Post subject: Reply with quote

Chevalier

Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
Hi,

Are you sure you should use soap over http? For me --based on the information from the exception you posted-- it seems that you use just web app with http POST and provide you information at the url parameters?

--
marko
Back to top
View user's profile Send private message Visit poster's website
sandip_gaikwad
PostPosted: Tue Dec 20, 2011 1:04 am    Post subject: SOAPREQUEST NODE ERROR Reply with quote

Voyager

Joined: 25 Jul 2011
Posts: 95
I have used HTTPRequest Node and it worked fine
But my requirement is to use SOAPRequest Node for the same
Back to top
View user's profile Send private message
marko.pitkanen
PostPosted: Tue Dec 20, 2011 1:27 am    Post subject: Reply with quote

Chevalier

Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
Hi,

If you use SOAP-nodes you have to use also WS -interface of your remote service. You have to generate message set based on the service description (wsdl + possible xsd.s) and use it to configure your SOAP-request node. You have to fill your soap request correctly (now it seems to be empty) and use correct url to invoke remote service and the remote service must response correctly according the service description it implements.

--
marko
Back to top
View user's profile Send private message Visit poster's website
smdavies99
PostPosted: Tue Dec 20, 2011 2:04 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
Quote:

I have used HTTPRequest Node and it worked fine
But my requirement is to use SOAPRequest Node for the same

Why?

You really do need to understand the difference between a raw HTTP request and a SOAP one.

Remember that SOAP (in this context) uses HTTP but nicely wraps the message up in a request/reply model.
It sounds like your use is more 'fire and forget'. If this is the case then use the HTTPRequestNode.

Is this a case of someone specifying the use of a protocol without understanding what using that protocol entails?

Sadly, we see this a lot of this sort of thing here
'I have a requirement to use xxxxx to do yyyyyy'.
Often xxxxx & yyyyyyy are mutually incompatible.


finally, as a help to everyone who read your posts can you go back an 'wrap' the lone lines in your original post? It is also nice to wrap them inside 'code' tags.
_________________
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.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAPREQUEST NODE ERROR
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
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.