Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-69375

HikariCP configuration not applied as expected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • pipeline-maven-plugin
    • None
    • Jenkins 2.346.3 // PostgreSQL API Plugin Version 42.3.3 // Pipeline Maven Integration Plugin Version 1161.v89a_7dcec5d31
    • 1195.v3b_a_d1b_e792e0

      I tried hard to set a parameter for the HikariCP but failed. As far as I understand the logic, calling setDataSourceProperties has a different effect then passing Properties to the public HikariConfig(Properties properties), which should have the intended behaviour.

      Having set DateSource and driver properties to maxLifetime=300000 leads to the following config output:

      Aug 18, 2022 9:25:03 AM FINE com.zaxxer.hikari.HikariConfig logConfiguration
      HikariPool-18 - configuration:
      Aug 18, 2022 9:25:03 AM FINE com.zaxxer.hikari.HikariConfig logConfiguration
      allowPoolSuspension................................false
      ...
      Aug 18, 2022 9:25:03 AM FINE com.zaxxer.hikari.HikariConfig logConfiguration
      dataSourceProperties................................{password=<masked>, maxLifetime=300000}
      Aug 18, 2022 9:25:03 AM FINE com.zaxxer.hikari.HikariConfig logConfiguration
      driverClassName................................none
      ...
      Aug 18, 2022 9:25:03 AM FINE com.zaxxer.hikari.HikariConfig logConfiguration
      maxLifetime................................1800000
      ...
      Aug 18, 2022 9:25:03 AM INFO com.zaxxer.hikari.HikariDataSource 
      HikariPool-18 - Starting...
      Aug 18, 2022 9:25:03 AM FINE com.zaxxer.hikari.util.DriverDataSource 
      

      So the given parameters are always passed in as data source properties and never configure the HikariCP.

      Can you please check this?

            bguerin Benoit
            andreasmandel Andreas Mandel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: