ServiceBus looks at the error reported by the client. Under the error information picture, how to troubleshoot?

Question

{"az.sdk.message":"Disposing of ReactorConnection.","connectionId":"MF_1e0f1e_1709916824303","isTransient":false,"isInitiatedByClient":false,"shutdownMessage":"Connection reset by peer, errorContext[NAMESPACE: cn-notification-analysis-service-service-buscnprd.servicebus.chinacloudapi.cn. ERROR CONTEXT: N/A]"}

Answer 1

Hi , Thanks for reaching out.

As per the error it is related to the connection between your application and the Service Bus. The error message "connection reset by peer" indicates that the connection was closed by the remote host. This can happen due to various reasons such as network issues, firewall settings, or server-side issues.

To troubleshoot this issue, you can try the following steps:

1. Check if there are any network issues or firewall settings that might be blocking the connection. You can try to connect to the Service Bus from a different network or machine to see if the problem persists. It might be your client network blocking the connection to the service bus
2. Check if there are any server-side issues with the Service Bus. You can check the Service Bus status page to see if there are any known issues or outages.

NOTE: Similar thread please check this [https://learn.microsoft.com/en-us/answers/questions/1342705/facing-connection-reset-by-peer-errorcontext(names](https://learn.microsoft.com/en-us/answers/questions/1342705/facing-connection-reset-by-peer-errorcontext(names) , where issue was with firewall as a firewall rule that was missing and blocking the connectivity from our client app to ASB , so please check this first , it may help

Kindly accept answer , if it helps , Thankyou!

Answer 2

Hi ,

If it occurs occasionally , please check these two things as well

1. Monitor the throughput and resource utilization of your Service Bus namespace. Intermittent connection resets could occur if the namespace is experiencing high throughput or resource contention. Consider scaling up the throughput units or optimizing the workload to reduce the load on the namespace.
2. Investigate the network stability between your client application and the Service Bus namespace. Check for any network congestion, latency issues, or packet loss that could be causing intermittent connection resets.