digdeep

 

 

生成环境的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,

 

分类:

技术点:

相关文章:

  • 2022-03-01
  • 2021-12-12
  • 2021-10-08
  • 2022-12-23
  • 2022-03-06
  • 2021-12-11
  • 2021-04-07
  • 2022-12-23
猜你喜欢
  • 2021-09-03
  • 2022-12-23
  • 2021-12-13
  • 2022-12-23
  • 2022-12-23
  • 2021-09-24
  • 2021-07-10
相关资源
相似解决方案