Anu Thomas

Hi @TheDevOps, thank you for reviewing the points and sharing your feedback. Let me address first those questions that may be pending to move forward with the deployments - 1....

Hi @TheDevOps, wanted to update you about release of the next version of azure-messaging-servicebus. • This version resolves an internal race between IO Thread and worker/timer threads. • It improves...

Hi @TheDevOps, thank you for sharing the update. I've been thinking and sketching some flow diagrams based on the INFO logs you shared. If you remember you mentioned (also I...

Hi @TheDevOps, that sounds like a plan! If the opt-in is set up properly, we should observe the following INFO log from the class "com.azure.core.amqp.implementation.RequestResponseChannelCache", > [INFO] Waiting for channel...

Hi @TheDevOps, thank you for getting back with observations and logs. Looking at the logs, we can see logs statements originated from `AmqpChannelProcessor`, which should not happen when the flag...

Hi again @TheDevOps, to follow up on your observation on an occurrence of _status-code: 401, status-description: InvalidSignature: The token has an invalid signature_, I scanned through the logs. The library...

Hello @TheDevOps, good morning!, thanks for the response. Yes, it’s recommended to use opt-in for Sender as well. you’re correct—the opt-in syntax for Sender remains the same. Just a small...

@TheDevOps, glad to hear that the issue has been resolved. Thanks for providing summary; it will certainly be helpful for others with similar use cases. Between as I promised offline,...

For those who are reading, this comment is not about the RCA of the original issue but discusses how certain CPU settings could theoretically cause the Service Bus client to...

Closing this, I'll leave a comment when the Service Bus library that opt-in the flag by default is released.