Anu Thomas

@akshit-mehta-rubrik are you looking into delete all the messages in the queue? We are developing a feature that can delete them in bulk, which is in [beta state](https://search.maven.org/artifact/com.azure/azure-messaging-servicebus/7.18.0-beta.1/jar) right now.

Hello @mohjohfox, seeing "delivery not on receive link" means that client’s link (connection) to the Service Bus entity (e.g. queue, topic) was lost by the time application was attempting to...

Hi @akshit-mehta-rubrik, you can find details of batch-delete here https://learn.microsoft.com/en-us/azure/service-bus-messaging/batch-delete The feature is in the process of getting ready for GA. Unlike receive-complete, the batch-delete optimized for bulk delete, for...

Closing this, reason for the log message provided and updating processor to 7.17.0 resolved the error happening on _complete_ calls

Hello @dakshme, I investigated this. The synchronous `receiveMessages(,)` API is designed to be invoked "serially". Underneath, each `receiveMessages(,)` synchronous invocation enqueue a work to pull the message. Each such work...

Hello @dakshme, I’ve got to prepare and run more tests. Once it passes and proves change can be shipped, I’ll update plan around ship date and version of SDK. Thanks...

@dakshme, btw, could you let me know the service tier?

Hello @dakshme, I was trying to find an official documentation about Standard tier and came across [this](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-throttling). My understanding from the above documentation about Standard tier is – 1. For...

Hello @dakshme, receiving 100 messages will reduce the namespace-throttling-credit by 100 not by 1. Even though it’s a single `receiveMessages` call in SDK, in response to that call, over the...

Hello @dakshme, to answer your question on lock expiry messages A reason for seeing "the lock expired" is: Consider application called `receiveMessages(100, 5-sec)`. The Client will send 100 AMQP-Credit to...