You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once we have switched to Bolt client, we are struggling with a very specific issue which can be rerpoduced in our real project (in other words, we didn't manage to create a sample project that repeats the issue).
The preliminary steps are like this:
Open some known page. This page queries Neo4j. Then several AJAX calls happen and they again query Neo4j.
Wait for 5min
Try to open any other page
In result we get the following exception:
Neo4j.Driver.ServiceUnavailableException: Failed after retried for 2 times in 30000 ms. Make sure that your database is online and retry again. ---> System.AggregateException: One or more errors occurred. ---> Neo4j.Driver.ServiceUnavailableException: Connection with the server breaks due to IOException: Unable to read data from the transport connection
We have the entire stack trace to provide, if you are interested.
Finally, next request to any page "restores" something under the hood, and everything starts working as usual.
We have looked over the server code that renders the first step's page and all subsequent AJAX calls, but we didn't find any smelly code. We suspect something wrong is done with async/await usage, but we use LindhartAnalyser and also our eyes are opened wide.
Did you see anything similar before? Could you please guide us to any direction?
The text was updated successfully, but these errors were encountered:
Hi Charlotte,
Once we have switched to Bolt client, we are struggling with a very specific issue which can be rerpoduced in our real project (in other words, we didn't manage to create a sample project that repeats the issue).
The preliminary steps are like this:
In result we get the following exception:
We have the entire stack trace to provide, if you are interested.
Finally, next request to any page "restores" something under the hood, and everything starts working as usual.
We have looked over the server code that renders the first step's page and all subsequent AJAX calls, but we didn't find any smelly code. We suspect something wrong is done with async/await usage, but we use LindhartAnalyser and also our eyes are opened wide.
Did you see anything similar before? Could you please guide us to any direction?
The text was updated successfully, but these errors were encountered: