首页 > 其他 > 详细

ActiveMq报错Channel was inactive for too (>30000)long

时间:2018-12-04 16:08:54      阅读:532      评论:0      收藏:0      [点我收藏+]

 

 

生成环境的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报错Channel was inactive for too (>30000)long

原文:https://www.cnblogs.com/digdeep/p/10064566.html

(0)
(0)
   
举报
评论 一句话评论(0
关于我们 - 联系我们 - 留言反馈 - 联系我们:wmxa8@hotmail.com
© 2014 bubuko.com 版权所有
打开技术之扣,分享程序人生!