azure-servicebus-queues

I keep getting MessageLockLostExceptions when processing messages. I am using Microsoft.Azure.ServiceBus 3.2.0 with .NET Core 2.1. I have a queue with LockDuration set to 30 seconds already containing a number of messages to be processed. I took the very basic message-receiving tutorial code from https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues#receive-messages-from-the-queue , which works fine. Now I want to simulate a slightly longer running message processing task (but still well within LockDuration ) by adding Task.Delay(10_000) . But

I need to split processing sequence (like in this question How to organize sequence of data processors with .net RX ) into several computation units in Azure environment. The idea is to serialize Observable sequence to Azure Queues(or Service Bus) and to deserialize it back. If producer or consumer is failed other party should be able to continue producing/consuming. Could anyone suggest an elegant way to do so and what to use (Azure Queues or Service Bus)? Has anyone used TCP Observable provider - http://rxx.codeplex.com/wikipage?title=TCP%20Qbservable%20Provider for such problems is it safe

I have logic app that is triggered by a service bus. The message content is not usable as it is just random characters. I suspect that perhaps it needs to be parsed but it is not clear how to do this. I have the following: Not enough reputation to add an image - but screen shot from Azure "Insert_Entity": { "inputs": { "body": { "PartitionKey": "deviceID", "RowKey": "@variables('curDate')", "content": "@triggerBody()?['ContentData']" }, When I look at the data that I am getting for the "content" coming from the "@triggerBody()?['ContentData']" it looks like this: "W3sidHlwZSI6ImxvZyJ9LF...." I

I'm having a hard time understanding the RetryExponential class that is used in conjunction with QueueClients (and I assume SubscriptionClients as well). The properties are listed here , but I don't think my interpretation of their descriptions is correct. Here's my interpretation... var minBackoff = TimeSpan.FromMinutes(5); // wait 5 minutes for the first attempt? var maxBackoff = TimeSpan.FromMinutes(15); // all attempts must be done within 15 mins? var deltaBackoff = TimeSpan.FromSeconds(30); // the time between each attempt? var terminationTimeBuffer = TimeSpan.FromSeconds(90); // the

We're trying to consume Azure Service Bus in a Node application. Our requirement is to fetch multiple messages from a queue . Since Azure SDK for Node doesn't support batch retrieval, we decided to use AMQP. While we're able to fetch messages using Peek Messages as described here ( https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-amqp-request-response#message-operations ). What we are noticing is that as soon as messages are fetched, they are getting removed from the queue. I am wondering if anyone has an insight into how we can fetch messages in "PeekLock" mode using

In Azure Service Bus, you can send a brokered message using QueueClient and MessageFactory . I would like to know why would you want to use one over the other. Azure Service Bus provides different way to send/receive messages. You can use the QueueClient to send and receive message to/from a queue. You can use the TopicClient to send message to a topic And you can use the SubscriptionClient to receive message from a subscription. Using MessageSender and MessageReceiver , you create sender and receiver that are entity type invariant: var factory = MessagingFactory.CreateFromConnectionString(

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 notify clients from the hub. However, I am not able to find a way to communicate the webjob and the hub

Can someone offer some more guidance on the use of the Azure Service Bus OnMessageOptions.AutoRenewTimeout http://msdn.microsoft.com/en-us/library/microsoft.servicebus.messaging.onmessageoptions.autorenewtimeout.aspx as I haven't found much documentation on this option, and would like to know if this is the correct way to renew a message lock My use case: 1) Message Processing Queue has a Lock Duration of 5 minutes (The maximum allowed) 2) Message Processor using the OnMessageAsync message pump to read from the queue (with a ReceiveMode.PeekLock) The long running processing may take up to 10