从死信队列重新提交消息-Azure Service Bus [英] Resubmitting a message from dead letter queue - Azure Service Bus

查看:137
本文介绍了从死信队列重新提交消息-Azure Service Bus的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经在Azure中创建了服务总线队列,并且运行良好.而且,如果未在默认尝试(10次)内传递邮件,则表示已将邮件正确地移到了死信队列中.

I have created a service bus queue in Azure and it works well. And if the message is not getting delivered within default try (10 times), it is correctly moving the message to the dead letter queue.

现在,我想将此消息从死信队列中重新提交回它起源的队列,并查看它是否再次起作用.我已经使用服务总线资源管理器尝试过相同的方法.但是它立即被移到了死信队列中.

Now, I would like to resubmit this message from the dead letter queue back to the queue where it originated and see if it works again. I have tried the same using service bus explorer. But it gets moved to the dead letter queue immediately.

是否可以这样做,如果可以,怎么办?

Is it possible to do the same, and if so how?

推荐答案

当您修复并重新提交死信队列中的消息时,Service Bus Explorer工具始终会创建原始消息的副本.两者没有什么不同,因为默认情况下,Service Bus消息传递不提供任何消息修复和重新提交机制.我建议您调查一下为什么您的消息最终在死信队列及其克隆中最终落入死信队列中.希望这会有所帮助!

The Service Bus Explorer tool always creates a clone of the original message when you repair and resubmit a message from the deadletter queue. It could not be any different as by default Service Bus messaging does not provide any message repair and resubmit mechanism. I suggest you to investigate why your message gets ends up in the deadletter queue as well as its clone when you resubmit it. Hope this helps!

这篇关于从死信队列重新提交消息-Azure Service Bus的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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