Closed neeraj-metallic closed 2 months ago
@anuchandy could you please take a look?
In the log I see that indeed the TCP connection recovered, re-established a new link to the queue entity (with name testqueue*). Is there any chance that the app logic in the processor handler stuck? no message will be delivered on the new link until the handler resume
Closing this. The log about connection close is normal (e.g. idle timeout). As observed in the log, the SDK will make a new connection if the current one is closed. Please refer above comment, in case there is no message delivery after post re-connection log.
Describe the bug The connection to receive messages from ServiceBusProcessorClient is closed due to inactivity in service bus and it was not able to recreate the connection.
Exception or Stack Trace
To Reproduce Steps to reproduce the behavior:
Code Snippet
Expected behavior
Setup (please complete the following information):
Application is written in Java and is running in Azure Kubernetes Service Bus is in Azure