简体繁体 English

Azure 服务总线 - 订阅和 DLQ

[英]Azure Service Bus - Subscriptions and DLQ

原文 2019-10-18 06:01:55 7 1 java/ azure/ publish-subscribe/ azureservicebus

I have recently started working on Azure Service Bus module which is currently used in our project.我最近开始研究我们项目中当前使用的 Azure 服务总线模块。 The current model is that, we send message to a topic and the topic has multiple subscriptions.当前的 model 是，我们向一个主题发送消息，该主题有多个订阅。 There is no filter for subscriptions and the subscribers consume it(Currently not looking to add filters).订阅没有过滤器，订阅者使用它（目前不希望添加过滤器）。

Question: Let's say there is 1 topic and 3 subscriptions.问题：假设有 1 个主题和 3 个订阅。 The message sent to topic is broadcasted to all subscriptions and applications from two subscriptions consume it.发送到主题的消息被广播到所有订阅，并且来自两个订阅的应用程序使用它。 Application for the third subscription goes down and the message is not consumed.第三次订阅的申请挂了，消息没有被消费。

What happens to the message from the 3rd subscription, will it be sent to Dead Letter Queue after TTL第 3 次订阅的消息会发生什么情况，是否会在 TTL 后发送到死信队列
Is there a way to find out, for which subscription the message wasn't consumed有没有办法找出消息没有被消费的订阅

1 个解决方案

What happens to the message from the 3rd subscription, will it be sent to Dead Letter Queue after TTL第 3 次订阅的消息会发生什么情况，是否会在 TTL 后发送到死信队列

If subscription is configured to dead-letter expired messages, yes, that's what will happen.如果订阅配置为死信过期消息，是的，这就是将会发生的事情。

Is there a way to find out, for which subscription the message wasn't consumed有没有办法找出消息没有被消费的订阅

You shouldn't do that.你不应该那样做。 Topics and subscriptions are intended to implement Pub/Sub pattern and is about decoupling the senders from the receivers.主题和订阅旨在实现 Pub/Sub 模式，并将发送者与接收者分离。