ActiveMQ:一条待处理消息,但队列为空 [英] ActiveMQ: One Pending Message but Queue is empty

查看:338
本文介绍了ActiveMQ:一条待处理消息,但队列为空的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我对ActiveMQ有一个奇怪的问题.我的队列似乎有待处理的消息,但是当我打开队列时,没有消息.

这是怎么了?是否真的有待处理的消息?如何将消息带回或至少看到内容?

未决消息的屏幕截图:

打开队列时的屏幕截图,该队列为空:

刚发现ActiveMQ 5.6.0的这两个bug.这可能是这个问题的根源吗?

与未确认的重新连接后,持久子项的pendingQueueSize的报告不正确

OrderPendingList中的问题可能导致持久子重新连接后无法传递邮件.

解决方案

所以我很早以前就更新到ActiveMQ 5.7.0,此后就再也没有此错误.所以我想说我的问题是由于这里的错误所致:

在与未经确认的连接重新连接后,持久子项的pendingQueueSize的报告不正确

OrderPendingList中的问题可能导致在持久子重新连接后无法传递邮件.

I have a strange problem with ActiveMQ. I have a queue that seems to have a pending message, but when I open the queue, there is no message.

What is wrong here? Is there really a message pending? How can I bring the message back or at least see the content?

Screenshot of the pending message:

Screenshot when opening the queue, which is empty:

EDIT: Just found these two bugs of ActiveMQ 5.6.0. Can this be the source of that problem?

Incorrect reporting of pendingQueueSize of durable subs after reconnect with unacked

Problem in OrderPendingList can lead to message not being deliver after durable sub reconnect.

解决方案

So I updated to ActiveMQ 5.7.0 quite some time ago and didn't had this bug anymore since. So I'd say my problem was due to these bugs here:

Incorrect reporting of pendingQueueSize of durable subs after reconnect with unacked

Problem in OrderPendingList can lead to message not being deliver after durable sub reconnect.

这篇关于ActiveMQ:一条待处理消息,但队列为空的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆