[FEATURE REQ] Manual message lock renewal when using ServiceBusProcessor

Library or service name. Azure.Messaging.ServiceBus

Is your feature request related to a problem? Please describe. I would like a way to manually renew the lock of a ServiceBusReceivedMessage when receiving messages through the ProcessMessageAsync message handler of a ServiceBusProcessor.

Using a ServiceBusReceiver to receive messages gives access to ServiceBusReceiver.RenewMessageLockAsync(ServiceBusReceivedMessage message, CancellationToken cancellationToken), but that call is unavailable through the ProcessMessageEventArgs argument of a ServiceBusProcess.ProcessMessageAsync message handler delegate.

I know there is the ServiceBusProcessorOptions.MaxAutoLockRenewalDuration option to use, but in my case a call may take anyway from less than a second, up to several hours. I want to be able to handle renewals manually, in order to make sure we are not stuck somewhere unexpected.

[Stolpe]

Luckily, I don’t use sessions, but thanks for letting me know.

[JoshLove-msft]

Ah, I understand now. I never realized I could create both a processor and a receiver, and use them interchangeably, but when I think of it it will probably be a perfectly good solution for me.

Thank you very much for your time, and have a nice day.

Yeah it works in this particular case because renewing a message lock doesn’t interfere with receiving messages. Interestingly, it would not work if you were using sessions as you need a session lock to renew the session, which means you couldn’t have both a processor and a receiver for the same session.