ActiveMq報錯Channel was inactive for too (>30000)long

 

 

生成環境的activemq 隔一到兩週,就報錯:apache

查看 activeme的日誌:tcp

2018-12-04 11:59:44,744 | WARN  | Transport Connection to: tcp://127.0.0.1:63807 failed: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://127.0.0.1:63807 | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ InactivityMonitor Workeride

channel tcp://127.0.0.1:63807 沒有被使用,超過了30000毫秒,修改連接參數:日誌

constructor-arg name="brokerURL" value="tcp://127.0.0.1:61616?wireFormat.maxInactivityDuration=0"/>orm

加上了 ?wireFormat.maxInactivityDuration=0 server

ActiveMQ stop inactivity read check

You can do the following to fix the issues:

1) Append max inactivity duration to your Uri in the format below: wireFormat.maxInactivityDuration=0blog

2) Use the same Uri at the client side as well as at the server sideget

Regards,it

相關文章
相關標籤/搜索