Anu Thomas

I wrote the test code (as shown below) that uses "One Receiver Client per One Thread model". I ran it for some time, with this approach I was able to...

Now I've the above code, you can ignore my earlier [questions](https://github.com/Azure/azure-sdk-for-java/issues/37594#issuecomment-1813188487) around repro code.

Hello, @dakshme, good to hear that the initial testing is positive. The reason for no or less occurrence of error on complete call is likely is due to disabling the...

Hello @dakshme, 1. The beta line is currently going through customer and in-house testing. Overall, the feedback is positive, and beta is stable. If all goes well, we plan the...

Hello @dakshme, for production deployments, I would strongly suggest using a coarse timeout in the range 3-5 seconds. If you remember, earlier we discussed the importance of coarse timeout, and...

Hi @dakshme, thank you for the additional context. Looking at the below log message you shared, >> {"az.sdk.message":"Transient error occurred." … It seems the environment is loading 7.14.x version or...

Hello @ dakshme, I started an offline discussion with you on this, so we can look into actual usage and discuss/plan how to resolve this.

From similar cases, there is a potential for _random_ thread bottleneck, can we rule out that? 1. App should ensure that any event processing and related business logic are completed...

The library internally uses Reactor to abstract all concurrency, and do not explicitly manage task scheduling. Reactor thread pools have no fairness guarantees, and underneath certain concurrency operators shares these...

Thanks for sharing the update. I've been thinking about this. Can you try the following temporary configurations as an experiment and see it make any difference for halt-and-resume behavior in...