[BUG] Message sending not retried after blocking timeout expired

[s-vivien]

Using com.azure:azure-messaging-servicebus:7.17.6, I am creating a ServiceBusSenderClient with the default retryOptions.

That gives me a ServiceBusSenderAsyncClient with the following retryOptions :

retryOptions = {AmqpRetryOptions@13509} 
 delay = {Duration@18397} "PT0.8S"
 maxDelay = {Duration@18398} "PT1M"
 maxRetries = 3
 retryMode = {AmqpRetryMode@18400} "EXPONENTIAL"
 tryTimeout = {Duration@18399} "PT1M"

And the ServiceBusSenderClient with this tryTimeout :

tryTimeout = {Duration@18407} "PT4M5.6S"
 nanos = 600000000
 seconds = 245

Every now and then, some messages can't be send and fails with the following error :

java.lang.IllegalStateException: Timeout on blocking read for 245600000000 NANOSECONDS
	at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:129)
	at reactor.core.publisher.Mono.block(Mono.java:1807)
	at com.azure.messaging.servicebus.ServiceBusSenderClient.sendMessage(ServiceBusSenderClient.java:266)

I don't know the root cause of the error, but I would expect the message sending to be retried, but it is not.
It waits for the whole Mono block timeout (245 seconds) and from what I understand this timeout error is not retriable, but I would expect a earlier timeout issued after the retryOptions.tryTimeout = PT1M.

Am I missing something ?

[github-actions]

@anuchandy @conniey @lmolkova

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[anuchandy]

Closing this, since this is same as 43877 which includes additional information