I also met this situation,and I set a exception listener,when the
exception listener listened this kind of exception.it will redo the sub.
And i also tried setting the maxIn..=0.but it has a bug,i reported it
long time ago.
lurker wrote:
>
> I'm programming some kind of messaging program that sends messages in
> sparse frequency using activeMQ.
> I got exceptions like following and connection between client and activeMQ
> server is closed.
> ----------
> 11:20:24,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:20:39,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:20:39,202 DEBUG [InactivityMonitor] Message received since last read
> check, resetting flag:
> 11:20:54,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:21:09,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:21:09,202 DEBUG [InactivityMonitor] Message received since last read
> check, resetting flag:
> 11:21:24,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:21:39,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:21:39,202 DEBUG [InactivityMonitor] Message received since last read
> check, resetting flag:
> 11:21:54,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:22:09,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:22:09,202 DEBUG [InactivityMonitor] Message received since last read
> check, resetting flag:
> 11:22:24,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:22:39,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:22:39,202 DEBUG [InactivityMonitor] Message received since last read
> check, resetting flag:
> 11:22:54,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:23:09,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:23:09,202 DEBUG [InactivityMonitor] No message received since last read
> check for tcp://aaa.aaa.aaa/111.111.111.111:61616! Throwing
> InactivityIOException.
> 11:23:09,218 WARN [ActiveMQConnection] Async exception with no exception
> listener: org.apache.activemq.transport.InactivityIOException: Channel was
> inactive for too long: some.domain.com/som.ip.he.re:61616
> org.apache.activemq.transport.InactivityIOException: Channel was inactive
> for too long: some.domain.com/som.ip.he.re:61616
> at
> org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:108)
> 11:23:09,218 DEBUG [TcpTransport] Stopping transport
> tcp://some.domain.com/som.ip.he.re:61616
> 11:23:09,218 WARN [ActiveMQConnection] Async exception with no exception
> listener: java.net.SocketException: socket closed
> java.net.SocketException: socket closed
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(Unknown Source)
> at
> org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
> at
> org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
> at java.io.DataInputStream.readInt(Unknown Source)
> at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
> at
> org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
> at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
> at java.lang.Thread.run(Unknown Source)
> ------------
>
> I don't know what is the problem.
> Please help me.
> Thanks in advance.
>
>
--
View this message in context:
http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p16116806.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
