You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We migrate from old azure servicebus sdk to the new one and we have a couple of of problems after the first deployment. Here's one of them:
We get several errors with the message:
...
Caused by: java.lang.IllegalStateException: Timeout on blocking read for 10400000000 NANOSECONDS
at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:123)
at reactor.core.publisher.Mono.block(Mono.java:1766)
at com.azure.messaging.servicebus.ServiceBusSenderClient.sendMessage(ServiceBusSenderClient.java:266)
....
Here's the setup of the sender:
public ServiceBusSenderClient prepareSender(String queueName) {
return new ServiceBusClientBuilder()
.connectionString(....)
.retryOptions(RETRY_OPTIONS)
.sender()
.queueName(queueName)
.buildClient();
}
We migrate from old azure servicebus sdk to the new one and we have a couple of of problems after the first deployment. Here's one of them:
We get several errors with the message:
...
Caused by: java.lang.IllegalStateException: Timeout on blocking read for 10400000000 NANOSECONDS
at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:123)
at reactor.core.publisher.Mono.block(Mono.java:1766)
at com.azure.messaging.servicebus.ServiceBusSenderClient.sendMessage(ServiceBusSenderClient.java:266)
....
One timestamp: "@timestamp":"2025-01-06T15:01:40.831Z"
queue: tos_trace_queue
namespace: sbus-nonprod-sprint-main-pextnk
Sdk version: 7.17.7
Java version: 17
RETRY_OPTIONS are created using this code:
Where from the 10400000000 NANOSECONDS timeout comes and how can we avoid it?
Thanks,
Cristi
The text was updated successfully, but these errors were encountered: