| Author |
Message
|
| bharathi.tech12 |
 Posted: Tue Dec 17, 2013 6:17 am Post subject: Error sending custom soap response when timeout soap fault |
 |
|
Voyager
Joined: 14 May 2013
Posts: 93
|
We have SOAPINPUT node and configured the Max Client wait time as 20 (sec). When the wait time reached HTTP Timeout terminal mapped to Mapper node and try to send the custom soap reply to our client but we are getting the below error and this error reply send to the client.
| Code: |
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Body>
<soapenv:Fault>
<soapenv:Code>
<soapenv:Value>soapenv:Receiver</soapenv:Value>
</soapenv:Code>
<soapenv:Reason>
<soapenv:Text xml:lang="en">BIP3113E: Exception detected in message flow MEC_Service_flow.SOAP Input (broker PRODBKR002)</soapenv:Text>
</soapenv:Reason>
<soapenv:Node>://localhost:7800/dcf/services/MecService (timeout)</soapenv:Node>
<soapenv:Detail>
<Text>BIP3752E: The SOAP Reply node 'MEC_Service_flow.Error 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/slot1/S800_P/src/WebServices/WSLibrary/ImbSOAPReplyNode.cpp: 396: ImbSOAPReplyNode::evaluate: ComIbmSOAPReplyNode: MEC_Service_flow#FCMComposite_1_13
BIP3701E: A Java exception was thrown whilst calling the Java JNI method ''Axis2Invoker_sendReplyDataNonSoap''. The Java exception was ''org.apache.axis2.AxisFault: Tried to send Non-Fault message when only a Fault message is allowed to be sent back during timeout processing.''. The Java stack trace was ''Frame : 0 org.apache.axis2.AxisFault: Tried to send Non-Fault message when only a Fault message is allowed to be sent back during timeout processing.| @: com.ibm.broker.axis2.Axis2Invoker.sendReplyInternalNotThroughPipeline(Axis2Invoker.java:1482)| @: com.ibm.broker.axis2.Axis2Invoker.sendReplyDataNonSoap(Axis2Invoker.java:1383)| @: com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)| @: com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)| @: com.ibm.broker.ct.mapping.MappingNode.buildAndPropagate(MappingNode.java:671)| @: com.ibm.broker.ct.mapping.MappingNode.evaluate(MappingNode.java:398)| @: com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)|''.
Correct the error, and if necessary redeploy the flow. : /build/slot1/S800_P/src/WebServices/WSLibrary/ImbSOAPReplyHelper.cpp: 707: ImbSOAPReplyHelper::makeSOAPReply: :</Text>
</soapenv:Detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
|
Please let me know how to handle this issues in flow.
 |
|
| Back to top |
|
 |
| mgk |
| Posted: Tue Dec 17, 2013 6:49 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi, that exception is saying that your custom reply must be a SOAP Fault reply.
_________________
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 |
|
|
| bharathi.tech12 |
| Posted: Tue Dec 17, 2013 6:58 am Post subject: |
|
|
Voyager
Joined: 14 May 2013
Posts: 93
|
Thanks for reply.
I got it. But the issues is we wand to send only soap reply with our custom message structure not the soap fault (MB build-in/Custom fault). Also in our wsdl we did not configure the fault details.
if that so how to handle it. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Dec 17, 2013 7:45 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
May I humbly suggest that you get the WSDL changed to reflect the real situation and include appropriate fault handlings functionality?
It has been a while since I looked at the SOAP nodes in detail but you might be able make it send the appropriate HTTP 500 class error code back to the caller.
_________________
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 |
|
|
| bharathi.tech12 |
| Posted: Tue Dec 17, 2013 9:23 am Post subject: |
|
|
Voyager
Joined: 14 May 2013
Posts: 93
|
Thanks for reply and suggestions.
But my problem is now its not so easy to add this fault message in wsdl and moving to prod.
Is this the only solution or any other way we can handle this?
I have doubt also, if suppose, HTTP time out terminal mapped to soap reply node instead of mapped to mapping node to create custom soap reply.
What type of response caller will get?
If there any sample response pls post it here.
  |
|
| Back to top |
|
|
|
|
