|
|
|
@ -32,7 +32,7 @@ the agent jar. See below for details.
|
|
|
|
|
<dependency>
|
|
|
|
|
<groupId>com.zaxxer</groupId>
|
|
|
|
|
<artifactId>HikariCP</artifactId>
|
|
|
|
|
<version>1.1.8</version>
|
|
|
|
|
<version>1.1.9</version>
|
|
|
|
|
<scope>compile</scope>
|
|
|
|
|
</dependency>
|
|
|
|
|
|
|
|
|
@ -41,7 +41,7 @@ the agent jar. See below for details.
|
|
|
|
|
<dependency>
|
|
|
|
|
<groupId>com.zaxxer</groupId>
|
|
|
|
|
<artifactId>HikariCP-agent</artifactId>
|
|
|
|
|
<version>1.1.8</version>
|
|
|
|
|
<version>1.1.9</version>
|
|
|
|
|
<scope>compile</scope>
|
|
|
|
|
</dependency>
|
|
|
|
|
|
|
|
|
@ -103,6 +103,11 @@ This property controls the number of milliseconds to delay between attempts to a
|
|
|
|
|
connection to the database. If ``acquireRetries`` is 0, this property has no effect.
|
|
|
|
|
*Default: 750*
|
|
|
|
|
|
|
|
|
|
``connectionInitSql``<br/>
|
|
|
|
|
This property sets a SQL statement that will be executed after every new connection creation
|
|
|
|
|
before adding it to the pool. If this SQL is not valid or throws an exception, it will be
|
|
|
|
|
treated as a connection failure and the standard retry logic will be followed. *Default: none*
|
|
|
|
|
|
|
|
|
|
``connectionTestQuery``<br/>
|
|
|
|
|
This is for "legacy" databases that do not support the JDBC4 Connection.isValid() API. This
|
|
|
|
|
is the query that will be executed just before a connection is given to you from the pool to
|
|
|
|
@ -184,6 +189,9 @@ method, like so:
|
|
|
|
|
config.addDataSourceProperty("user", "SA");
|
|
|
|
|
config.addDataSourceProperty("password", "");
|
|
|
|
|
|
|
|
|
|
See the [Initialization](#initialization) section below for further examples.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
##### ***Missing Knobs*** #####
|
|
|
|
|
|
|
|
|
|
HikariCP has plenty of "knobs" to turn as you can see above, but comparatively less than some other pools.
|
|
|
|
|