IDEMPIERE-5013 set HikariCP initial pool size to 10 - as it was in c3p0 (#2083)

- Applying the same as we did in commit f76c39889c for PostgreSQL
- For some reason c3p0 was configured with MaxPoolSize=150 for oracle (90 for PostgreSQL) - setting same default
This commit is contained in:
Carlos Ruiz 2023-11-02 05:49:48 +01:00 committed by GitHub
parent bbeab2ba27
commit b2e863fd0f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions

View File

@ -42,7 +42,7 @@ connectionTimeout=60000
# recommend not setting this value and instead allowing HikariCP to act as a # recommend not setting this value and instead allowing HikariCP to act as a
# fixed size connection pool. # fixed size connection pool.
# Default: same as maximumPoolSize # Default: same as maximumPoolSize
#minimumIdle= minimumIdle=10
# This property controls the maximum size that the pool is allowed to reach, # This property controls the maximum size that the pool is allowed to reach,
# including both idle and in-use connections. Basically this value will determine # including both idle and in-use connections. Basically this value will determine
@ -52,7 +52,7 @@ connectionTimeout=60000
# will block for up to connectionTimeout milliseconds before timing out. Please # will block for up to connectionTimeout milliseconds before timing out. Please
# read about pool sizing: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing # read about pool sizing: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
# Default: 10 # Default: 10
maximumPoolSize=90 maximumPoolSize=150
# This property controls the maximum lifetime of a connection in the pool. An # This property controls the maximum lifetime of a connection in the pool. An
# in-use connection will never be retired, only when it is closed will it then be # in-use connection will never be retired, only when it is closed will it then be