-
-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timed out error after being idle for a long time #577
Comments
Hi @xiusin, Can you tell me on what operating system and with what database it happens? |
@Fabio286 It should be that the idle objects in the database object pool have not been released. This is not specific to any operating system, and can occur on both macOS and Windows. If there is no activity for a long time, request timeouts may occur and the only solution is to disconnect the connection. |
The database libraries used in Antares implement different ways to handle connections. Therefore, it would be helpful for me to understand which database you encountered these errors with. I am considering implementing a keepalive and retry system to have better control over these kinds of situations. |
pgsql, mysql |
The text was updated successfully, but these errors were encountered: