azure-servicebus-queues

来源： https://stackoverflow.com/questions/63585687/azure-service-bus-how-to-renew-lock

问题 Theoretically it looks like azure service bus queues is one to one with respect to message and receiver. Just wanted to know if it's possible to have more than one listeners to a queue. If it is 1:1, does it mean to realize competing consumers pattern we cannot use queues, and topics is the only option? 回答1: There is a big difference between queues and topics: with queues, each message is picked up by only 1 consumer . With a topic, every consumer that subscribed to the topic will get each

问题 We have a distributed architecture and there is a native system which needs to be called. The challenge is the capacity of the system which is not scalable and cannot take on more load of requests at same time. We have implemented Service Bus queues, where there is a Message handler listening to this queue and makes a call to the native system. The current challenge is whenever a message posted in the queue, the message handler is immediately processing the request. However, We wanted to have

问题 We have a distributed architecture and there is a native system which needs to be called. The challenge is the capacity of the system which is not scalable and cannot take on more load of requests at same time. We have implemented Service Bus queues, where there is a Message handler listening to this queue and makes a call to the native system. The current challenge is whenever a message posted in the queue, the message handler is immediately processing the request. However, We wanted to have

问题 It is very hard to find some good documentation on getting all the messages in a deadletter queue and getting to take a peek at them. I have an Azure Servicebus Queue and everything I can find is for Azure Servicebus Topics. Can someone help me with a quick guide? 回答1: Dead letter queue is a secondary sub-queue where the poison messages are moved to. In case of Azure Servicebus Queue the standard path for DLQ is queuePath/$DeadLetterQueue . So you need to have another queueClient to read the

问题 It is very hard to find some good documentation on getting all the messages in a deadletter queue and getting to take a peek at them. I have an Azure Servicebus Queue and everything I can find is for Azure Servicebus Topics. Can someone help me with a quick guide? 回答1: Dead letter queue is a secondary sub-queue where the poison messages are moved to. In case of Azure Servicebus Queue the standard path for DLQ is queuePath/$DeadLetterQueue . So you need to have another queueClient to read the

问题 Apologies, I'm new to Azure. I created a service bus and queue via the Azure portal using this tutorial. I can write and read from the queue ok. The problem is, to deploy to the next environment, I have to either update the ARM template to add the new queue or create the queue in code. I can't create the queue through the portal in the next environment. I've chosen the latter: check to see if the queue exists and create as required via code. I already have an implementation for this for a

问题 I am trying to find more information about "Active Connections", "Connections Opened" and "Connections Closed" in Azure Service Bus Metrics. Can someone help me finding a good document to understand these "Active Connections", "Connections Opened" and "Connections Closed" in Azure Service Bus ? 回答1: Active Connections - the number of active connections on a namespace as well as on an entity. Connections Opened - The number of open connections. Connections Closed - The number of closed

问题 I am trying to find more information about "Active Connections", "Connections Opened" and "Connections Closed" in Azure Service Bus Metrics. Can someone help me finding a good document to understand these "Active Connections", "Connections Opened" and "Connections Closed" in Azure Service Bus ? 回答1: Active Connections - the number of active connections on a namespace as well as on an entity. Connections Opened - The number of open connections. Connections Closed - The number of closed

问题 So I have an azure function acting as a queue trigger that calls an internally hosted API. There doesn't seem to be a definitive answer online on how to handle a message that could not be processed due to issues other than being poisonous. An example: My message is received and the function attempts to call the API. The message payload is correct and could be handled however the API/service is down for whatever reason (this time will likely be upwards of 10 minutes). Currently what happens is