-
Notifications
You must be signed in to change notification settings - Fork 270
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
Connection to Postgres database closed #5458
Comments
Thank you for reporting an issue! Pinging @jsenko to respond or triage. |
I suspect you need to do something like set Lines 79 to 80 in 2bca64b
|
And if you're wondering why we did that, it's so we can support multiple storage configurations from a single container image. Now with 3.0 we support the following storages but only have a single back-end container image:
Much easier for everyone hopefully. Thanks @wolfchimneyrock for suggesting a fix. @jabbrwcky can you confirm if it worked for you? |
Hi, also encountered this issue. And already have a fix for this: #5507 |
As Eric said, this is mainly due to the support of multiple sql variants within the same container image. In previous versions Quarkus did not had the ability to deactivate a datasource at runtime. This capability has been introduced relatively recently, and I'm planning on exploring that to see if we can go back to use Quarkus standard properties so any standard jdbc config can be added without the need for configuring it manually in the producer. I'll get back to this as soon as I can get past some CI issues we're having right now. |
This has been addressed as part of the PR I have attached. The maximum lifetime for the datasource (and any other property, really) can be configured using Quarkus standards (see this) for more information. |
Description
After some time running the database connection to postgres is closed and the registry apparently is unable to handle it.
Also trying to use keepalive does not help:
jdbc:postgresql://postgres.apicurio.svc.cluster.local/apicurio?tcpKeepAlive=true
Registry Version: 3.0.3
Persistence type: sql
Environment
Kubernetes 1.30
Postgres v 12 (as StatefulSet)
Steps to Reproduce
Expected vs Actual Behaviour
I expected the application not to drop the connection or at least to recover from it.
Logs
The text was updated successfully, but these errors were encountered: