azure-servicebus-queues

问题 I need to process incoming messages on Azure. Each message will be associated with a specific entity – say, through an EntityId property – and messages belonging to the same entity must be processed in-order with respect to each other. At the same time, I would to preserve the serverless aspect of Azure Functions; if I have steady streams of messages for 1,000 entities, I'd like to have 1,000 concurrent executions of my function. I haven't found a clean way of achieving this. Service Bus

问题 I've looked everywhere for information on this but can't seem to find what i'm looking for. I've got an azure topic, with one subscription. The handler for the subscription failed some messages, they've been put on the deadletter queue. I can access the messages but i'm at a loss for how to restore them. I don't want to create a copy of the message and send it to the topic. I specifically want to move it to the subscription queue it came from. Is there any way to do this? 回答1: I don't know if

问题 I have the following scenario: I have an azure webjob (used to send mails) and I need to check the progress of the webjob in my web application. I am using SignalR to communicate with clients from my server. When I want to send an email, I push a message in the queue and the azure webjob does his job. The question is, how can I communicate the progress of the webjob to the client? Originally my idea was to push a message from the webjob, so the Hub could read it from the queue. Then, I would

问题 I'm trying to come up with the best way to schedule a message for an Azure service bus queue or topic while leaving the option open for immediately sending a message instead of the scheduled message. I want to make sure I can protect myself against creating a duplicate message if I try to send the replacement message right at or after the scheduled time of the first message. What will happen if I try to cancel a scheduled message with CancelScheduledMessageAsync (for both QueueClient and

问题 I'm trying to read a message from an Azure ServiceBus queue using an Azure WebJob but it's throwing and exception: Unhandled Exception: System.InvalidOperationException: Found 2 DNS claims in authorization context. I've set the correct connection strings named "AzureWebJobsServiceBus", "AzureWebJobsDashboard" and "AzureWebJobsStorage" The WebJob Program code has been updated to use JobHostConfiguration: class Program { static void Main() { var config = new JobHostConfiguration(); config

问题 I'm trying to figure out what is the best practice for using Service Bus from a Web-API. I've read that re-creating objects like QueueClient, SubscriptionClient and etc' is the wrong approach, so I need to reusing factories and clients. Service Bus client objects, such as Microsoft.ServiceBus.Messaging.QueueClient or Microsoft.ServiceBus.Messaging.MessageSender, are created through a MessagingFactory object, which also provides internal management of connections. You should not close

问题 So the scenario is that I'm using an SB queue to throttle outgoing callbacks to other services. One of the standard problems with calling back to other services is that they may be down for uncontrollable amounts of time. Assuming I detect that the target is down/not responding, what is the best pattern for abandoning that message so that it doesn't reappear on the queue immediately? Here's are some approaches I'm either aware of, have tried or am considering: Obviously if I just use

问题 How do you get the count of dead letter messages in an Azure Service Bus queue? I can get the count in the queue like so ... var ns = NamespaceManager.CreateFromConnectionString(sbConnectionString); var queue = ns.GetQueue(queueName); var count = queue.MessageCount; But this looks to include both messages in the queue, and also messages in the associated dead letter queue How can I differentiate between them? 回答1: Do take a look at MessageCountDetails property in QueueDescription. You will

问题 I need to get a message from queue in some special time. So I use scheduled message in queue. I send messages via ScheduleMessageAsync method. For getting messages I use Azure Web Job with ServiceBusTrigger. I send a couple of messages, everything works fine on my side, but in Azure Portal, if I go to page with my queue I see that I have negative amount of messages in queue. I had this problem some days ago, but then it disappeared, but now appears again. Is it problem in my logic or just a

问题 I'm using MassTransit as my messaging framework, running on top of Azure Service Bus. I'm running MassTransit from inside a WebJob (although I don't think that matters) Now I'm trying to get MassTransit to process multiple messages at the same time, as I'm now dealing with messages that individually take a while to process. So to speed up performance, I don't want each message to be processed one by one. I tried setting MaxConcurrentCalls to , for example, 30, but that doesn't seem to do it.