| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP3113E while using Async SOAP Request |
« View previous topic :: View next topic » |
| Author |
Message
|
| skvk |
 Posted: Wed Dec 10, 2008 1:01 pm Post subject: BIP3113E while using Async SOAP Request |
 |
|
Newbie
Joined: 10 Dec 2008
Posts: 1
|
I am getting the error - BIP3113E: Exception detected in message flow.
My wsdl ends with ? wsdl.
The reason for this error is not the ?WSDL because I am able to access 5 other wsdls like this.
Using a SOAP Request node returns - Request timed out message.
Using a Async SOAP Request node returns the below message. However, I am able to successfully invoke this wsdl using the soapUI client.
What could be the problem here?
Details when Async SOAP Request is used:
<faultcode>soapenv:Server</faultcode>
<faultstring>BIP3113E: Exception detected in message flow Elig1MS.FreshEligTestMF.SOAP Input (broker WBRK61_DEFAULT_BROKER)</faultstring>
- <detail>
<Text>BIP2230E: Error detected whilst processing a message in node 'Elig1MS.FreshEligTestMF.SOAP Asynchronous Request'. The message broker detected an error whilst processing a message in node 'Elig1MS.FreshEligTestMF.SOAP Asynchronous Request'. An exception has been thrown to cut short the processing of the message. See the following messages for details of the error. : F:\build\S610_P\src\DataFlowEngine\TemplateNodes\ImbRequestTemplateNode.cpp: 417: ImbRequestTemplateNode::processMessageAssemblyToFailure: ImbRequestTemplateNode: Elig1MS/FreshEligTestMF#FCMComposite_1_5 BIP3162S: An HTTP error occurred. The HTTP Request-Line was: ''POST /FacetsWebServiceLibrary441/FaWsvcInpProcessEligRange.asmx HTTP/1.1 ''. The HTTP Request Header bitstream (if any) to be used was: 'X'436f6e74656e742d4c656e6774683a20313535310d0a436f6e74656e742d547970653a20746578742f786d6c3b20636861727365743d7574662d380d0a4163636570743a206170706c69636174696f6e2f736f61702b786d6c2c206170706c69636174696f6e2f64696d652c206d756c7469706172742f72656c617465642c20746578742f2a0d0a557365722d4167656e743a2049424d20576562205365727669636573204578706c6f7265720d0a43616368652d436f6e74726f6c3a206e6f2d63616368650d0a507261676d613a206e6f2d63616368650d0a486f73743a2036332e37382e3137372e3134350d0a534f4150416374696f6e3a2022220d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a0d0a''. The HTTP Request Message Body bitstream (if any) to be used was: 'X'3c3f786d6c2076657273696f6e3d22312e302220656e636f64696e673d227574662d38223f3e3c736f6170656e763a456e76656c6f706520786d6c6e733a7873643d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d612220786d6c6e733a71303d22687474703a2f2f7472697a6574746f2e636f6d2f6678692f69736c2f466157737663496e7050726f63657373456c696752616e67652220786d6c6e733a736f6170656e763d22687474703a2f2f736368656d61732e786d6c736f61702e6f72672f736f61702f656e76656c6f70652f2220786d6c6e733a7873693d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d612d696e7374616e6365223e3c736f6170656e763a48656164657220786d6c6e733a7773613d22687474703a2f2f7777772e77332e6f72672f323030352f30382f61646472657373696e67223e3c7773613a546f20736f6170656e763a6d757374556e6465727374616e643d2231223e687474703a2f2f36332e37382e3137372e3134352f466163657473576562536572766963654c6962726172793434312f466157737663496e7050726f63657373456c696752616e67652e61736d783c2f7773613a546f3e3c7773613a5265706c79546f20736f6170656e763a6d757374556e6465727374616e643d2231223e3c7773613a416464726573733e687474703a2f2f3136352e3235332e33392e3133393a373830312f574d422f4173796e632f526573706f6e73652f4e6f64652f50726f63657373456c69675f4e6f64653f636f6e746578743d616335343166303026616d703b74696d657374616d703d313139313538353c2f7773613a416464726573733e3c7773613a5265666572656e6365506172616d65746572733e3c776d623a636f6e7465787420786d6c6e733a776d623d22687474703a2f2f7777772e69626d2e636f6d2f776d622f323030372f30352f7270223e3c776d623a6f7065726174696f6e4e616d653e50726f63657373456c696752616e67655f4d656d6265724b65793c2f776d623a6f7065726174696f6e4e616d653e3c776d623a7265706c794964656e7469666965723e62303534316630303c2f776d623a7265706c794964656e7469666965723e3c776d623a74696d655374616d703e313139313538353c2f776d623a74696d655374616d703e3c2f776d623a636f6e746578743e3c2f7773613a5265666572656e6365506172616d65746572733e3c2f7773613a5265706c79546f3e3c7773613a4d657373616765494420736f6170656e763a6d757374556e6465727374616e643d2231223e75726e3a757569643a333539343233443141413446424642323136313232383933393537383239313c2f7773613a4d65737361676549443e3c7773613a416374696f6e20736f6170656e763a6d757374556e6465727374616e643d2231223e687474703a2f2f7472697a6574746f2e636f6d2f6678692f69736c2f466157737663496e7050726f63657373456c696752616e67652f57656253766350726f63657373456c696752616e6765536f61702f50726f63657373456c696752616e67655f4d656d6265724b6579526571756573743c2f7773613a416374696f6e3e3c2f736f6170656e763a4865616465723e3c736f6170656e763a426f64793e3c71303a50726f63657373456c696752616e67655f4d656d6265724b65793e3c71303a70436f6e6669673e3c71303a4661636574734964656e746974793e3030303030303030323336363c2f71303a4661636574734964656e746974793e3c71303a526567696f6e3e47564253434644323434313c2f71303a526567696f6e3e3c2f71303a70436f6e6669673e3c71303a704d454d455f434b3e313435323c2f71303a704d454d455f434b3e3c71303a7046524f4d5f44543e323030382d31322d31305430303a30303a30303c2f71303a7046524f4d5f44543e3c71303a70544f5f44543e323030382d31322d31305430303a30303a30303c2f71303a70544f5f44543e3c2f71303a50726f63657373456c696752616e67655f4d656d6265724b65793e3c2f736f6170656e763a426f64793e3c2f736f6170656e763a456e76656c6f70653e''. The HTTP Reply Header bitstream (if any) received from the server was: 'X'485454502f312e312035303020496e7465726e616c20536572766572204572726f720d0a446174653a205765642c2031302044656320323030382032303a30353a353820474d540d0a5365727665723a204d6963726f736f66742d4949532f362e300d0a582d506f77657265642d42793a204153502e4e45540d0a582d4173704e65742d56657273696f6e3a20322e302e35303732370d0a43616368652d436f6e74726f6c3a20707269766174650d0a436f6e74656e742d547970653a20746578742f786d6c3b20636861727365743d7574662d380d0a436f6e74656e742d4c656e6774683a203430350d0a0d0a''. The HTTP Reply Message Body bitstream (if any) received from the server was: 'X'3c3f786d6c2076657273696f6e3d22312e302220656e636f64696e673d227574662d38223f3e3c736f61703a456e76656c6f706520786d6c6e733a736f61703d22687474703a2f2f736368656d61732e786d6c736f61702e6f72672f736f61702f656e76656c6f70652f2220786d6c6e733a7873693d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d612d696e7374616e63652220786d6c6e733a7873643d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d61223e3c736f61703a426f64793e3c736f61703a4661756c743e3c6661756c74636f64653e736f61703a436c69656e743c2f6661756c74636f64653e3c6661756c74737472696e673e53657276657220646964206e6f74207265636f676e697a65207468652076616c7565206f6620485454502048656164657220534f4150416374696f6e3a202e3c2f6661756c74737472696e673e3c64657461696c202f3e3c2f736f61703a4661756c743e3c2f736f61703a426f64793e3c2f736f61703a456e76656c6f70653e''. Ensure that the HTTP data is valid. See the following messages for information pertaining to this error. : F:\build\S610_P\src\WebServices\WSLibrary\ImbSOAPRequestNode.cpp: 2098: ImbSOAPRequestNode::logWebServiceInvocationException: : BIP3692S: A SOAP Async Request node encountered an HTTP error whilst making an HTTP Request. The HTTP Request was made to the destination ''//63.78.177.145/FacetsWebServiceLibrary441/FaWsvcInpProcessEligRange.asmx''. The HTTP Status-Line returned was: ''HTTP/1.1 500 Internal Server Error''. An error occurred whilst performing an HTTP Request. Check that the remote server is responding and that the request is specified correctly. See the following messages for information pertaining to this error. : F:\build\S610_P\src\WebServices\WSLibrary\ImbSOAPRequestNode.cpp: 1106: ImbSOAPRequestNode::requestData: ImbRequestTemplateNode: Elig1MS/FreshEligTestMF#FCMComposite_1_5</Text>
</detail> |
|
| Back to top |
|
 |
| mgk |
| Posted: Wed Dec 10, 2008 2:16 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
According to the error you posted, you sent the following :
Content-Length: 1551
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: IBM Web Services Explorer
Cache-Control: no-cache
Pragma: no-cache
Host: 63.78.177.145
SOAPAction: ""
Connection: keep-alive
{msg body}
And the server returned:
HTTP/1.1 500 Internal Server Error
Date: Wed, 10 Dec 2008 20:05:58 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Content-Length: 405
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>Server did not recognize the value of HTTP Header SOAPAction: .</faultstring><detail /></soap:Fault></soap:Body></soap:Envelope>
Which is pretty clear! So does your WSDL define a SOAPAction for the operation you are invoking. If not you will need to change the WSDL to add one or speficy one explicitly in the HTTPRequestHeaders folder.
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
