You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "ying (JIRA)" <ji...@apache.org> on 2009/03/09 16:05:39 UTC
[jira] Created: (AMQ-2152) Slave Exception Channel was inactive for
too long
Slave Exception Channel was inactive for too long
-------------------------------------------------
Key: AMQ-2152
URL: https://issues.apache.org/activemq/browse/AMQ-2152
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.2.0
Environment: Solaris 10
Activemq 5.2.0
Reporter: ying
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2152) Slave Exception Channel was inactive for
too long
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Snyder updated AMQ-2152:
------------------------------
Fix Version/s: 5.5.0
(was: 5.4.1)
> Slave Exception Channel was inactive for too long
> -------------------------------------------------
>
> Key: AMQ-2152
> URL: https://issues.apache.org/activemq/browse/AMQ-2152
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.2.0
> Environment: Solaris 10
> Activemq 5.2.0
> Reporter: ying
> Fix For: 5.5.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2152) Slave Exception Channel was inactive for
too long
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies updated AMQ-2152:
----------------------------
Fix Version/s: 5.4.0
> Slave Exception Channel was inactive for too long
> -------------------------------------------------
>
> Key: AMQ-2152
> URL: https://issues.apache.org/activemq/browse/AMQ-2152
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.2.0
> Environment: Solaris 10
> Activemq 5.2.0
> Reporter: ying
> Fix For: 5.4.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2152) Slave Exception Channel was inactive for
too long
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated AMQ-2152:
---------------------------------
Fix Version/s: 5.4.1
(was: 5.4.0)
> Slave Exception Channel was inactive for too long
> -------------------------------------------------
>
> Key: AMQ-2152
> URL: https://issues.apache.org/activemq/browse/AMQ-2152
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.2.0
> Environment: Solaris 10
> Activemq 5.2.0
> Reporter: ying
> Fix For: 5.4.1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.