2018-09-24T11:18:47.901Z ["<tns:sendTransaction><arg0><![CDATA[<C24TRANREQ><STAN>537787897359</STAN><TRAN_DATE_TIME>20180924121817</TRAN_DATE_TIME>
<TRAN_AMT>54000</TRAN_AMT><PROCESSING_CODE>50</PROCESSING_CODE><TRAN_CRNCY_CODE>MZN</TRAN_CRNCY_CODE><COUNTRY_CODE>MOZ</COUNTRY_CODE><VALUE_DATE>20180924</VALUE_DATE>
<DR_ACCT_NUM>990050002256</DR_ACCT_NUM><CR_ACCT_NUM>010020003471</CR_ACCT_NUM><RESERVED_FLD_1>SBF/UTU/Almo&#xE7;os</RESERVED_FLD_1>
</C24TRANREQ> ]]></arg0></tns:sendTransaction>"] error: {"root":{"Envelope":{"Body":{"Fault":{"faultcode":"soapenv:Server","faultstring":"BIP3113E:
 Exception detected in message flow finaclews.wsrequest (broker IHDEVBRK1)","detail":{"Text":"BIP3752E: The SOAP Reply node 'finaclews.wsreply'
 encountered an error while processing a reply message. \nAn error occurred during reply message processing.
\nSee previous error messages to determine the cause of the error. : /build/slot1/S000_P/src/WebServices/WSLibrary/ImbSOAPReplyNode.cpp:
 397: ImbSOAPReplyNode::evaluate: ComIbmSOAPReplyNode: finaclews#FCMComposite_1_3\nBIP3701E: A Java exception was thrown whilst calling the Java JNI method
 ''Axis2Invoker_sendReplyDataSoap''. 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.sendReplyDataSoap(Axis2Invoker.java:1127)|''. \nCorrect the error, and if necessary redeploy the flow.
 : /build/slot1/S000_P/src/WebServices/WSLibrary/ImbSOAPReplyHelper.cpp: 767: ImbSOAPReplyHelper::makeSOAPReply: :"}}}}},
"response":{"statusCode":500,"body":"<?xml version=\"1.0\" encoding=\"utf-8\"?><soapenv:Envelope xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\">
<soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>BIP3113E: Exception detected in message flow finaclews.wsrequest (broker IHDEVBRK1)
</faultstring><detail><Text>BIP3752E: The SOAP Reply node 'finaclews.wsreply' encountered an error while processing a reply message.
 \nAn error occurred during reply message processing. \nSee previous error messages to determine the cause of the error.
 : /build/slot1/S000_P/src/WebServices/WSLibrary/ImbSOAPReplyNode.cpp: 397: ImbSOAPReplyNode::evaluate: ComIbmSOAPReplyNode:
 finaclews#FCMComposite_1_3\nBIP3701E: A Java exception was thrown whilst calling the Java JNI method ''Axis2Invoker_sendReplyDataSoap''.
 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.sendReplyDataSoap(Axis2Invoker.java:1127)|''.
 \nCorrect the error, and if necessary redeploy the flow. : /build/slot1/S000_P/src/WebServices/WSLibrary/ImbSOAPReplyHelper.cpp: 767: ImbSOAPReplyHelper::makeSOAPReply: :
 </Text></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>","headers":{"server":"Apache-Coyote/1.1","wmb-timeoutflow":"true","content-type":"text/xml;charset=utf-8"
,"content-length":"1551","date":"Mon, 24 Sep 2018 11:17:42 GMT","connection":"close"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"172.20.238.38:7802",
"port":"7802","hostname":"172.20.238.38","hash":null,"search":null,"query":null,"pathname":"/cba/wbs","path":"/cba/wbs","href":"http://172.20.238.38:7802/cba/wbs"},"method":"POST",
"headers":{"User-Agent":"node-soap/0.23.0","Accept":"text/html,application/xhtml+xml,application/xml,text/xml;q=0.9,*/*;q=0.8","Accept-Encoding":"none","Accept-Charset":"utf-8",