Skip to content

Commit 40c9335

Browse files
committed
ConnectionLostException
1 parent 1422629 commit 40c9335

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

articles/azure-relay/relay-exceptions.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,18 @@ There are two common causes for this error:
7373

7474
Occasionally, the Relay service might experience delays in processing requests. It might happen, for example, during periods of high traffic. If it occurs, retry your operation after a delay, until the operation is successful. If the same operation continues to fail after multiple attempts, check the [Azure service status site](https://azure.microsoft.com/status/) to see if there are known service outages.
7575

76+
## ConnectionLostException - NameRenewalFailed
77+
78+
### Symptoms
79+
Your client receives the exception: `Microsoft.Azure.Relay.ConnectionLostException : InternalServerError: NameRenewalFailed`.
80+
81+
### Cause
82+
Azure Relay service restarts listener connections every 24 hours. This behavior is by design. The Azure Relay service disconnects a listener active connection every 24 hours, and the listener will reconnect with the server using the retry mechanism.
83+
84+
### Resolution
85+
No action on your part as the listener automatically reconnects to the server. If you notice that your listener isn't connecting again, [submit a ticket](https://azure.microsoft.com/support/options/) to the support team.
86+
87+
7688
## Next steps
7789
* [Azure Relay FAQs](relay-faq.yml)
7890
* [Create a relay namespace](relay-create-namespace-portal.md)

0 commit comments

Comments
 (0)