You are currently browsing legacy 3.0 version of documentation. Click here to switch to the newest 4.2 version.

We can help you with migration to the latest RavenDB

Contact Us Now
see on GitHub

The Azure router timeout

Symptoms:

  • Exception is thrown in RavenDB client when accessing raven server, exception was because of socket timeout or general connection failure
  • Problem happens mainly on Azure hosted VMs

Cause:

Azure's load balancer closes connections that are idle for more than 60 seconds

Resolution:

We have to make sure that there are no connections that are idle for more than 60 seconds. There are two possible ways to do that:

  • Make sure that RavenDB is accessed at least once a minute (consider having a keep-alive message)
  • Change service point manager's MaxIdleTime value in your client application

Further read:

Azure Sql Server Connection Management