You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Aaron Phillips (JIRA)" <ji...@apache.org> on 2011/07/27 15:39:09 UTC
[jira] [Issue Comment Edited] (AMQ-3418) CLONE - Slave Exception
Channel was inactive for too long
[ https://issues.apache.org/jira/browse/AMQ-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071715#comment-13071715 ]
Aaron Phillips edited comment on AMQ-3418 at 7/27/11 1:37 PM:
--------------------------------------------------------------
I am seeing the same thing. I have a master-slave pair and almost as frequently as once a day I see a message like this in the master broker's log, then the master broker goes down, leaving the slave up.
2011-07-26 22:41:10,810 | ERROR | Slave Failed | org.apache.activemq.broker.ft.MasterBroker | ActiveMQ NIO Worker
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: /172.16.10.123:33644
I have tried setting timeout like this in the slave's activemq xml config, but the error above, referencing 30k milli timout still happens, as if this setting has no effect.
tcp://masterbroker:61616?wireFormat.maxInactivityDuration=150000
I am attaching both the master and slave logs with DEBUG turned on. I am actually running 5.5.0, not 5.2.0 as the original issue is written. This is also running on CentOS 5.5
was (Author: adphillips):
I am seeing the same thing. I have a master-slave pair and almost as frequently as once a day I see a message like this in the master broker's log, then the master broker goes down, leaving the slave up.
2011-07-26 22:41:10,810 | ERROR | Slave Failed | org.apache.activemq.broker.ft.MasterBroker | ActiveMQ NIO Worker
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: /172.16.10.123:33644
I have tried setting timeout like this in the slave's activemq xml config, but the error above, referencing 30k milli timout still happens, as if this setting has no effect.
tcp://masterbroker:61616?wireFormat.maxInactivityDuration=150000
I am attaching both the master and slave logs with DEBUG turned on
> CLONE - Slave Exception Channel was inactive for too long
> ---------------------------------------------------------
>
> Key: AMQ-3418
> URL: https://issues.apache.org/jira/browse/AMQ-3418
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.5.0
> Environment: Solaris 10
> Activemq 5.2.0
> Reporter: Aaron Phillips
> Attachments: masterbroker.log.gz, slavebroker.log.gz
>
>
> 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)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira