| Author |
Message
|
| asrajesh |
 Posted: Mon Feb 04, 2013 6:05 am Post subject: Webservice call returning WSWS3400I failure |
 |
|
Novice
Joined: 19 Jan 2013
Posts: 20
|
Hi,
When calling webservice from our flow(using HTTPRequest node), we are receiving WSWS3400I failure response with the following message (in BLOB body)
| Code: |
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/>
<soapenv:Body>
<soapenv:Fault
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>soapenv:Server.generalException</faultcode>
<faultstring>WSWS3400I: Info: unexpected exception</faultstring>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope> |
Note:
The same service is working fine in one HP UNIX box and we are trying to implement the same service in another HP UNIX box. We receive this failure in NEW HP Unix box |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Mon Feb 04, 2013 6:08 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
What drives your decision to use the HTTPRequest node rather than the SOAPRequest node? What version of the product are you on?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| asrajesh |
| Posted: Mon Feb 04, 2013 7:08 am Post subject: |
|
|
Novice
Joined: 19 Jan 2013
Posts: 20
|
1. Since HTTPRequest node handle both SOAP as well as XML message, we went in for HTTPRequest node. Kindly note that the flow is working fine in other UNIX box.
2. We are using WMB version 7
Thanks
Regards
S. Rajesh |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Feb 04, 2013 7:36 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
If you are calling a web service, you should use the SOAPRequest node. What is the (default) code page of the qmgr on the old HP box? What is the (default) code page of the qmgr on the new HP box? What is the OS version of both systems? What is the effective level of the runtimes between the two boxes. Use mqsireportbroker to find out.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 04, 2013 8:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| asrajesh wrote: |
| Since HTTPRequest node handle both SOAP as well as XML message, we went in for HTTPRequest node. |
Explain to me the difference between an XML message and a SOAP message, given that a SOAP message is an XML message which conforms to an agreed standard.
Explain to me why you'd want to put both messages with and without a SOAP envelope through the same endpoint.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Feb 04, 2013 8:52 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Vitor wrote: |
| asrajesh wrote: |
| Since HTTPRequest node handle both SOAP as well as XML message, we went in for HTTPRequest node. |
Explain to me the difference between an XML message and a SOAP message, given that a SOAP message is an XML message which conforms to an agreed standard.
Explain to me why you'd want to put both messages with and without a SOAP envelope through the same endpoint. |
Good points, Vitor.
There are many reasons you may want to consider using SOAPRequest node over the HTTPRequest node. The SOAPRequest node requires a WSDL to match it's output and input XML structures. If a logical tree is presented to the SOAPRequest node, and the tree is missing a required element, the SOAPRequest node throws a validation error.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Mon Feb 04, 2013 5:46 pm Post subject: Re: Webservice call returning WSWS3400I failure |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| asrajesh wrote: |
When calling webservice from our flow(using HTTPRequest node), we are receiving WSWS3400I failure response with the following message (in BLOB body) :
| Code: |
| ...<faultcode>soapenv:Server.generalException</faultcode><faultstring>WSWS3400I: Info: unexpected exception.</faultstring>... |
|
This is an application-generated SOAP Fault. It is occurring within the web service, not within the message flow. Check any relevant web service logs for more useful information about the fault. |
|
| Back to top |
|
|
| asrajesh |
| Posted: Tue Feb 05, 2013 7:04 am Post subject: |
|
|
Novice
Joined: 19 Jan 2013
Posts: 20
|
Thank you very much ....
We found the issue. The issue was there was some extra spaces in the input message. We did a TRIM and the problem resolved..
String behaviour of broker..
Regards
S. Rajesh |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Feb 05, 2013 7:49 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| asrajesh wrote: |
| String behaviour of broker.. |
No, strange behavior of your code. Broker was doing what you told it to do.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
