| Author |
Message
|
| samgn123 |
 Posted: Tue Oct 08, 2013 2:02 am Post subject: IBM Integration Bus v9: SOAP MessageFlows unresponsive Linux |
 |
|
Newbie
Joined: 04 Nov 2008
Posts: 8
|
Hello all,
We have a message flow with SOAP Input node , exposed as Web Service developed. We have deployed the same on a broker in Linux environment.
The problem we are facing is , " If this SOAP Message flow , is left inactive / not invoked for a certain time , it becomes Un-Responsive. We need to restart the flow to get it working again. This is the case with all SOAP Flows deployed. This problem does not happen in Windows environment. Also other flows using MQ , do work without any issues.
Hence the problem is only with SOAP Flows deployed in Linux environment" . Please suggest if anyone has come acoss this problem or knows a fix on the same. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Oct 08, 2013 3:18 am Post subject: Re: IBM Integration Bus v9: SOAP MessageFlows unresponsive L |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| samgn123 wrote: |
Hello all,
We have a message flow with SOAP Input node , exposed as Web Service developed. We have deployed the same on a broker in Linux environment.
The problem we are facing is , " If this SOAP Message flow , is left inactive / not invoked for a certain time , it becomes Un-Responsive. We need to restart the flow to get it working again. This is the case with all SOAP Flows deployed. This problem does not happen in Windows environment. Also other flows using MQ , do work without any issues.
Hence the problem is only with SOAP Flows deployed in Linux environment" . Please suggest if anyone has come acoss this problem or knows a fix on the same. |
What is the service Id that you are running broker under ?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 08, 2013 4:36 am Post subject: Re: IBM Integration Bus v9: SOAP MessageFlows unresponsive L |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| lancelotlinc wrote: |
| samgn123 wrote: |
Hello all,
We have a message flow with SOAP Input node , exposed as Web Service developed. We have deployed the same on a broker in Linux environment.
The problem we are facing is , " If this SOAP Message flow , is left inactive / not invoked for a certain time , it becomes Un-Responsive. We need to restart the flow to get it working again. This is the case with all SOAP Flows deployed. This problem does not happen in Windows environment. Also other flows using MQ , do work without any issues.
Hence the problem is only with SOAP Flows deployed in Linux environment" . Please suggest if anyone has come acoss this problem or knows a fix on the same. |
What is the service Id that you are running broker under ? |
Ignore this completely.
You are facing a problem.
You need to troubleshoot that problem.
Nothing you have said so far indicates that you have done anything to troubleshoot the problem - merely that you have observed the problem, and restarted things randomly in case the problem would then "be fixed".
Troubleshoot the problem.
Provide a description of what occurs when you troubleshoot the problem.
In response, you will almost certainly receive helpful, directed, meaningful suggestions.
Or you can have a three page discussion with lancelotlinc that will take three or five days and leave you in the same place you're at right now.
It's your choice. |
|
| Back to top |
|
|
| samgn123 |
| Posted: Tue Oct 08, 2013 8:33 am Post subject: Troubleshooting |
|
|
Newbie
Joined: 04 Nov 2008
Posts: 8
|
Agreed. I posted the problem, so that if anyone has come across. While i am troubleshooting the same in parallel.
I also wanted to add and share that , In the execution group logs. Below error is logged.
2013-10-07 12:40:22.230624 Execution group started. UUID is: '9902e652-4001-0000-0080-d79fe958bba7'. Broker is: T02DIIB01
Exception in thread "Thread-31" 2013-10-08 07:48:27.869 53 BIP3184E: com.ibm.broker.axis2.MbSoapException: Warning: unable to send reply.
2013-10-08 07:48:27.874 53 at com.ibm.broker.axis2.Axis2Invoker.sendReplyDataNonSoap(Axis2Invoker.java:1430)
2013-10-08 07:48:27.876 53 Caused by: org.apache.axis2.AxisFault: Problem sending SOAP Reply
2013-10-08 07:48:27.877 53 at com.ibm.broker.axis2.Axis2Invoker.sendReplyInternalNotThroughPipeline(Axis2Invoker.java:1689)
2013-10-08 07:48:27.878 53 at com.ibm.broker.axis2.Axis2Invoker.sendReplyDataNonSoap(Axis2Invoker.java:1383)
2013-10-08 07:48:27.879 53 Caused by: java.net.SocketException: Broken pipe
2013-10-08 07:48:27.886 53 at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
2013-10-08 07:48:27.887 53 at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
2013-10-08 07:48:27.889 53 at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:215)
2013-10-08 07:48:27.890 53 at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:462)
2013-10-08 07:48:27.891 53 at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:119)
2013-10-08 07:48:27.893 53 at com.ibm.broker.inlinehttp.tomcatthreadpool.InlineHTTPOutputStream.reallyFlush(InlineHTTPOutputStream.java:163)
2013-10-08 07:48:27.894 53 at com.ibm.broker.inlinehttp.tomcatthreadpool.WMBOutboundHTTPTransport.finish(WMBOutboundHTTPTransport.java:230)
2013-10-08 07:48:27.895 53 at com.ibm.broker.axis2.Axis2Invoker.sendReplyInternalNotThroughPipeline(Axis2Invoker.java:1680)
2013-10-08 07:48:27.897 53 ... 1 more
Exception in thread "Thread-31" 2013-10-08 07:48:27.902 53 org.apache.axis2.AxisFault: Error: Trying to send a message when an attempt to send a reply has already been made. A previous attempt to send a reply may have been made, but the client connection canot be reused.
2013-10-08 07:48:27.904 53 at com.ibm.broker.axis2.Axis2Invoker.sendReplyInternalNotThroughPipeline(Axis2Invoker.java:1470)
2013-10-08 07:48:27.905 53 at com.ibm.broker.axis2.Axis2Invoker.sendReplyDataNonSoap(Axis2Invoker.java:1383)
Exception in thread "Thread-37" 2013-10-08 07:51:06.007 59 BIP3184E: com.ibm.broker.axis2.MbSoapException: Warning: unable to send reply.
2013-10-08 07:51:06.008 59 at com.ibm.broker.axis2.Axis2Invoker.sendReplyDataSoap(Axis2Invoker.java:1165)
2013-10-08 07:51:06.009 59 Caused by: org.apache.axis2.AxisFault: Problem sending SOAP Reply
2013-10-08 07:51:06.010 59 at com.ibm.broker.axis2.Axis2Invoker.sendReplyInternalNotThroughPipeline(Axis2Invoker.java:1689)
2013-10-08 07:51:06.010 59 at com.ibm.broker.axis2.Axis2Invoker.sendReplyDataSoap(Axis2Invoker.java:1127)
2013-10-08 07:51:06.011 59 Caused by: java.net.SocketException: Broken pipe
2013-10-08 07:51:06.011 59 at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
2013-10-08 07:51:06.012 59 at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
2013-10-08 07:51:06.012 59 at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:215)
2013-10-08 07:51:06.013 59 at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:462)
2013-10-08 07:51:06.014 59 at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:119)
2013-10-08 07:51:06.015 59 at com.ibm.broker.inlinehttp.tomcatthreadpool.InlineHTTPOutputStream.reallyFlush(InlineHTTPOutputStream.java:163)
2013-10-08 07:51:06.015 59 at com.ibm.broker.inlinehttp.tomcatthreadpool.WMBOutboundHTTPTransport.finish(WMBOutboundHTTPTransport.java:230)
2013-10-08 07:51:06.016 59 at com.ibm.broker.axis2.Axis2Invoker.sendReplyInternalNotThroughPipeline(Axis2Invoker.java:1680)
2013-10-08 07:51:06.016 59 ... 1 more
Exception in thread "Thread-37" 2013-10-08 07:51:06.018 59 org.apache.axis2.AxisFault: Error: Trying to send a message when an attempt to send a reply has already been made. A previous attempt to send a reply may have been made, but the client connection canot be reused.
2013-10-08 07:51:06.019 59 at com.ibm.broker.axis2.Axis2Invoker.sendReplyInternalNotThroughPipeline(Axis2Invoker.java:1470)
2013-10-08 07:51:06.019 59 at com.ibm.broker.axis2.Axis2Invoker.sendReplyDataSoap(Axis2Invoker.java:1127)
Exception in thread "Thread-30" 2013-10-08 07:51:19.347 52 BIP3184E: com.ibm.broker.axis2.MbSoapException: Warning: unable to send reply.
2013-10-08 07:51:19.348 52 at com.ibm.broker.axis2.Axis2Invoker.sendReplyDataNonSoap(Axis2Invoker.java:1430)
2013-10-08 07:51:19.348 52 Caused by: org.apache.axis2.AxisFault: IOException writing outputstream
2013-10-08 07:51:19.349 52 at com.ibm.broker.axis2.Axis2TransportSender.sendReply(Axis2TransportSender.java:441)
2013-10-08 07:51:19.350 52 at com.ibm.broker.axis2.Axis2HTTPTransportSender.invoke(Axis2HTTPTransportSender.java:129)
2013-10-08 07:51:19.350 52 at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:627)
2013-10-08 07:51:19.351 52 at com.ibm.broker.axis2.Axis2Invoker.sendReplyInternalThroughPipeline(Axis2Invoker.java:1798)
2013-10-08 07:51:19.351 52 at com.ibm.broker.axis2.Axis2Invoker.sendReplyDataNonSoap(Axis2Invoker.java:1403)
2013-10-08 07:51:19.352 52 Caused by: java.io.IOException: Stream closed due to HTTPConnector timeout
2013-10-08 07:51:19.352 52 at com.ibm.broker.inlinehttp.tomcatthreadpool.InlineHTTPOutputStream.write(InlineHTTPOutputStream.java:248)
2013-10-08 07:51:19.353 52 at com.ibm.broker.inlinehttp.tomcatthreadpool.WMBOutboundHTTPTransport.writeOutputMessageBody(WMBOutboundHTTPTransport.java:310)
2013-10-08 07:51:19.353 52 at com.ibm.broker.axis2.Axis2TransportSender.sendReply(Axis2TransportSender.java:328)
2013-10-08 07:51:19.354 52 ... 4 more |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Oct 08, 2013 8:49 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Code: |
Exception in thread "Thread-31" 2013-10-08 07:48:27.902 53 org.apache.axis2.AxisFault: Error: Trying to send a message when an attempt to send a reply has already been made. A previous attempt to send a reply may have been made, but the client connection canot be reused.
|
This is a common error in a webservice enviroment.
If you make a webservice call and you get a 500 class error response the 'handle' for that connection has been used up. If your code sometime later tries to reply then you will see this error.
It also happens when your webservice call timesout and then the response sent or tries to be sent back.
This may or may not be related to the problem you are seeing.
_________________
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 |
|
|
| lancelotlinc |
| Posted: Tue Oct 08, 2013 8:57 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| smdavies99 wrote: |
| Code: |
Exception in thread "Thread-31" 2013-10-08 07:48:27.902 53 org.apache.axis2.AxisFault: Error: Trying to send a message when an attempt to send a reply has already been made. A previous attempt to send a reply may have been made, but the client connection canot be reused.
|
This is a common error in a webservice enviroment.
If you make a webservice call and you get a 500 class error response the 'handle' for that connection has been used up. If your code sometime later tries to reply then you will see this error.
It also happens when your webservice call timesout and then the response sent or tries to be sent back.
This may or may not be related to the problem you are seeing. |
Make sure your code hits one and exactly only one SOAPReply node in any logic path.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Oct 08, 2013 2:14 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Completely normal and to be expected.
Putting the flow in debug will fire off your timeout terminal on the SOAP input node... unless your timeout is HUGE. Now you could put a breakpoint on the timeout path and not let that go until the response has been sent... But be aware that then the timeout will try and trigger the afore mentioned exception...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Oct 09, 2013 3:06 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| fjb_saper wrote: |
Completely normal and to be expected.
Putting the flow in debug will fire off your timeout terminal on the SOAP input node... unless your timeout is HUGE. Now you could put a breakpoint on the timeout path and not let that go until the response has been sent... But be aware that then the timeout will try and trigger the afore mentioned exception...
Have fun |
Sounds like a job for Trace node man !
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
