消息调度中的错误 [英] Bug in the message scheduling

问题描述

复制步骤:

1. 在空的Azure ServiceBus队列上安排了一条消息
2. 在活动之后但接收方对其进行处理之前，使用其scheduleId取消了消息调度
3. 仍处于活动状态，并且计划的消息数(在Azure门户上可见)减少了1(甚至低于0)

...因此，如果仅调度了一条消息，该消息现在处于活动状态并且已被取消，那么调度队列中的消息数为-1.

自2018年7月26日起，这将出现在ServiceBus服务中

解决方案

--------------- -------------------------------------------------- ------------------------------

如果此答案有帮助，请单击标记为答案"或向上" -投票".要提供有关您的论坛体验的其他反馈，请单击 在这里 >

Steps to reproduce:

1. A message is scheduled on the empty Azure ServiceBus Queue
2. The message scheduling is cancelled using its scheduleId after becoming active but before it is processed by the receiver
3. The message is still active and the number of scheduled messages (visible on the Azure portal) is decreased by 1 (even below 0)

... so if there was just 1 message scheduled that is now active and being cancelled then the number of messages in the schedule queue stands at -1. 

This is appearing in ServiceBus service as of 26 of July 2018

解决方案

Yes, it is a known issue with memory counting, but the runtime/messages are intact. The fix will be deployed in the next release which we expect in the next 30 days.

-----------------------------------------------------------------------------------------------

If this answer was helpful, click "Mark as Answer" or "Up-Vote". To provide additional feedback on your forum experience, click here

这篇关于消息调度中的错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！