Hi Anurag, I'm not sure how you've configured the ActiveMQ transport but take a look on this [1] and see if that helps. It clearly states that setting maxInactivityDuration to 0 would disable inactivity monitoring. But, you may want to set to some other value.
[1] http://activemq.apache.org/configuring-wire-formats.html Hope this helps, -Marcelo On Jun 6, 2011, at 4:03 PM, agujral wrote: > Hi All, > I using activmemq-5.4 I am seeing the following error messages: > org.apache.activemq.transport.InactivityIOException: Channel was inactive > for too long: /172.20.210.18:41140 > at > org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:236) > at > org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:85) > at > org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:104) > at > org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:40) > at > org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1247) > at > org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:808) > at > org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:844) > at > org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98) > at > org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36) > 2011-06-05 03:52:41,432 | INFO | Transport failed: > java.net.SocketException: Broken pipe | > org.apache.activemq.broker.TransportConnection.Transport | Async Exception > Handler > java.net.SocketException: Broken pipe > at java.net.SocketOutputStream.socketWrite0(Native Method) > at > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > at java.net.SocketOutputStream.write(SocketOutputStream.java:136) > at > org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:115) > at java.io.DataOutputStream.flush(DataOutputStream.java:106) > at > org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:181) > at > org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:244) > at > org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:85) > at > org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:104) > at > org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:40) > at > org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1247) > at > org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:808) > at > org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:844) > at > org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98) > at > org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36) > > I looked at the previous messages but could not really make out how to make > sure this does not occur again. > > Please Suggest. > > Thanks > Anurag > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Exception-Channel-was-inactive-for-too-long-tp3578274p3578274.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
