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

首先看下警告日志
在生产服务器上，如果长期没有使用到队列，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.Transport | InactivityMonitor Async Task: 
java.util.concurrent.ThreadPoolExecutor$Worker@6a346239
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://127.0.0.1:52659
    at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:187)
    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:680)

官网解释如下：

maxInactivityDuration=30000

The maximum inactivity duration (before which the socket is considered dead) in milliseconds. On some platforms it can take a long time for a socket to appear to die, so we allow the broker to kill connections if they are inactive for a period of time. Use by some transports to enable a keep alive heart beat feature. Set to a value <= 0 to disable inactivity monitoring.

Setting transport.useInactivityMonitor=false will disable the InactivityMonitor. Configuring wireFormat.maxInactivityDuration=0 will achieve the same result.

即：配置JMS连接最大闲置时间(消息服务器无消息)
该wireFormat.maxInactivityDuration 的默认值是30000ms
wireFormat.maxInactivityDuration=0 这样的参数， wireFormat.maxInactivityDuration是心跳参数。
避免ActiveMQ在一段时间没有消息发送时抛出 "Channel was inactive for too long"异常。该异常会关闭连接，虽然client端会重连成功，但是不能发送数据，然后继续报下面异常：

2014-10-30 00:49:49  [ ActiveMQ Task-3:529216111 ] - [ INFO ]  Successfully reconnected to tcp://132.97.122.168:61616
2014-10-30 00:49:49  [ ActiveMQ Transport: tcp:///132.97.122.168:61616@41298:529216129 ] - [ WARN ]  Transport (tcp://132.97.122.168:61616) failed, reason:  java.net.SocketException: Connection reset, attempting to automatically reconnect

<?xml version="1.0" encoding="UTF-8"?>
 
<beans xmlns="http://activemq.org/config/1.0">
 
  <broker brokerName="receiver">
    <transportConnectors>
      <transportConnector uri="tcp://localhost:62002"/>
    </transportConnectors>
 
    <networkConnectors>
      <networkConnector uri="static:(tcp://somehost:62001?wireFormat.maxInactivityDuration=0)"/>
    </networkConnectors>
 
    <persistenceAdapter>
      <memoryPersistenceAdapter/>
    </persistenceAdapter>
  </broker>
</beans>

解决方案如下:
　查看配置,在activemq的 conf/activemq.xml 里设置了InactivityMonitor的连接超时时间导致,如:
通过设置连接URL的属性:　tcp:/ / 0.0.0.0:61616 ? wireFormat.maxInactivityDuration = 30000,表示如果30秒没有数据被读取,接InactivityMonitor假定有一个连接的问题。 InactivityMonitor抛出一个InactivityIOException和关闭相关的转换连接.
解决方案：wireFormat.maxInactivityDuration=0，禁用InactivityMonitor

uri=“tcp://0.0.0.0:61616?wireFormat.maxInactivityDuration=30000”
1
修改为

uri=“tcp://0.0.0.0:61616?wireFormat.maxInactivityDuration=0”