ActiveMq报错Channel was inactive for too (>30000)long解决方案

最新推荐文章于 2025-05-14 09:29:32 发布

原创

最新推荐文章于 2025-05-14 09:29:32 发布 · 4.6k 阅读

1 ·

CC 4.0 BY-SA版权

首先看下警告日志
在生产服务器上，如果长期没有使用到队列，MQ Produce和consumer端同时报如下错误，导致不能正常工作。

Transport (tcp://132.97.122.168:61616) failed, reason: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://132.97.122.168:61616, attempting to automatically reconnect

 2012-06-26 17:13:55,712 | DEBUG | 30000 ms elapsed since last read check. | org.apache.activemq.transport.AbstractInactivityMonitor | InactivityMonitor ReadCheck
2012-06-26 17:13:55,712 | DEBUG | No message received since last read check for tcp:///127.0.0.1:52659! Throwing InactivityIOException. | org.apache.activemq.transport.AbstractInactivityMonitor | InactivityMonitor ReadCheck
2012-06-26 17:13:55,714 | DEBUG | Transport Connection to: tcp://127.0.0.1:52659 failed: 
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://127.0.0.1:52659 |
org.apache.activemq.broker.TransportConnection.Tra