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
Got database connection closed exception #742
Comments
Unfortunately I have not seen this issue before. Based on a little bit of googling, my best guess is that some other database error is happening (e.g. a transient connection issue between the app and the database) and is not being properly reported in the log (but is perhaps reported to the UI?). If that happens, then the connection might get closed but also returned to the connection pool, resulting in the 'connection has been closed' error later. Have you seen any other errors, perhaps in the UI only? How reproducible is this? Can you make it happen with some repeatable steps, or does it seem random? |
No, I didn't notice other errors before this exception. https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_wait_timeout |
Interesting. Does the timing of the error work out for this theory? How long does Apicurio run before this issue pops up? Here is the docker image for |
The time didn't match, it's about 30min in the recent case. |
OK much appreciated. If these settings take care of the issue then I'll obviously make sure we get them added as defaults. |
After a few days test run, It seems to be working.
|
Thanks for figuring this out, @askfor - very much appreciate the followup. I'll update the docker images and then document these settings in the apicurio documentation. |
Hi,
While we are trying apicurio, we got database connction closed exception from time to time.
We've tried postgresql and mysql, both databases have this problem, the first version we installed is 0.2.25, we have upgraded to 0.2.26, this problem still exists.
We are running apicruio in k8s use images from dockerhub.
Any ideas? Thanks.
The text was updated successfully, but these errors were encountered: