ActiveMQ stop inactivity read check

最新推荐文章于 2020-02-04 17:47:15 发布

最新推荐文章于 2020-02-04 17:47:15 发布 · 130 阅读

文章标签：

#ActiveMQ #Apache

JMS 专栏收录该内容

40 篇文章

订阅专栏

本文介绍了解决ActiveMQ中因通道长时间非活跃导致的异常问题。通过在TCP URL中添加特定参数?wireFormat.maxInactivityDuration=0，可以避免在没有消息发送时出现Channelwasinactivefortoolong异常。

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,

如果不这样设置，对应的错误会出现：
2008-05-07 09:22:56,343 [org.apache.activemq.ActiveMQConnection]-[WARN] Async exception with no exception listener: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long: localhost/127.0.0.1:61616
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long: localhost/127.0.0.1:61616

ActiveMQ的tcp url：tcp://localhost:61616后面要加入?wireFormat.maxInactivityDuration=0 这样的参数，否则当一段时间没有消息发送时会抛出 "Channel was inactive for too long"异常2008-06-17 17:22 通过网页