Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 27 Jul 2011 13:31:09 +0000 (UTC)
From: "Aaron Phillips (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1331323696.11848.1311773469636.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <657163904.11847.1311773349531.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3418) CLONE - Slave Exception Channel was
 inactive for too long
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron Phillips commented on AMQ-3418:
-------------------------------------

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.2.0
>         Environment: Solaris 10
> Activemq 5.2.0
>            Reporter: Aaron Phillips
>
> 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