Repository navigation
Keycloak v19.0.3 ignores --db-pool-max-size command line param #16153
anand-kulk
started this conversation in
Archive
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello - I am load testing Quarkus and using Postgres with default 100 max connections limit(including 3 for superuser). I am passing --db-pool-max-size=70 but keycloak still creates about 96 connections when it gets following error from postgres db.
org.keycloak.models.ModelException: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC ConnectionCaused by: org.postgresql.util.PSQLException: FATAL: remaining connection slots are reserved for non-replication superuser connectionsThis is in kubernetes and I can see the
--db-pool-max-sizeis correctly passed when calling kc.sh startup script. Is this a bug that Quarkus ignores the connection pool max setting? I also tried passing env varKC_DB_POOL_MAX_SIZEand didn't work. Please advise.See attached files -
All reactions