生成环境的activemq 隔一到两周,就报错:

查看 activeme的日志:

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 Worker
channel tcp://127.0.0.1:63807 没有被使用,超过了30000毫秒,修改链接参数:
constructor-arg name="brokerURL" value="tcp://127.0.0.1:61616?wireFormat.maxInactivityDuration=0"/>
加上了 ?wireFormat.maxInactivityDuration=0
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=0
2) Use the same Uri at the client side as well as at the server side
Regards,
本文详细描述了在ActiveMQ环境中遇到的链接超时错误,特别是在生成环境中隔一到两周就会出现的问题。通过分析日志,我们发现是由于通道长时间未被使用导致的,并提供了解决方案,即修改链接参数,加入?wireFormat.maxInactivityDuration=0来避免读取检查超时。
4711

被折叠的 条评论
为什么被折叠?



