[ 
https://issues.apache.org/activemq/browse/AMQ-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41366#action_41366
 ] 

Denis Abramov commented on AMQ-1592:
------------------------------------

I am using activemq-all-5.1-SNAPSHOT.jar and still get this error: 

2008-02-19 11:44:25,768 (ActiveMQConnection.java:1453) WARN  
org.apache.activemq.ActiveMQConnection - Async exception with no exception 
listener: org.apache.activemq.transport.InactivityIOException: Channel was 
inactive for too long. 
org.apache.activemq.transport.InactivityIOException: Channel was inactive for 
too long. 
        at 
org.apache.activemq.transport.InactivityMonitor.readCheck(InactivityMonitor.java:101)
 
        at 
org.apache.activemq.transport.InactivityMonitor.access$000(InactivityMonitor.java:35)
 
        at 
org.apache.activemq.transport.InactivityMonitor$1.run(InactivityMonitor.java:51)
 
        at 
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:431)
 
        at 
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.runAndReset(FutureTask.java:198)
 
        at 
edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:189)
 
        at 
edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:213)
 
        at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
 
        at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
 
        at java.lang.Thread.run(Thread.java:595) 




> Inactivity Monitor: org.apache.activemq.transport.InactivityIOException: 
> Channel was inactive for too long
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1592
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1592
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.1
>         Environment: RedHat Linux
>            Reporter: Denis Abramov
>            Priority: Blocker
>
> From a different poster:
> 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) 
> ------------ 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to