Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
5.5.0
-
None
-
None
-
CentOS 5.5
Activemq 5.5.0
Description
I have a master/slave setup on the same machine. Clients (consumers) are connecting to the master and they are all up and running for two days. There is no message produced and consumed during the period and then i will get the following:
2009-03-08 03:16:43,032 [$Worker@1f4577d] ERROR TransportConnection - Slave has exception: Channel was inactive for too long: /127.0.0.1:32803 shutting down master now
.
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long: /127.0.0.1:32803
at org.apache.activemq.transport.InactivityMonitor$5.run(InactivityMonitor.java:164)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
2009-03-08 03:16:43,032 [0.0.0.245:33220] ERROR MasterBroker - Slave Failed
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long: /127.0.0.1:32803
at org.apache.activemq.transport.InactivityMonitor$5.run(InactivityMonitor.java:164)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
2009-03-08 03:16:43,044 [0.0.0.245:33236] ERROR MasterBroker - Slave Failed
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long: /127.0.0.1:32803
at org.apache.activemq.transport.InactivityMonitor$5.run(InactivityMonitor.java:164)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Attachments
Attachments
Issue Links
- is a clone of
-
AMQ-2152 Slave Exception Channel was inactive for too long
- Closed