All connections created by the pool are monitored and will send information back to the connection pool’s logging output. Each log message contains a unique identifier for the connection involved, thereby allowing you to follow the operation of a single connection while several database operations are occurring simultaneously.

All calls to create or prepare new statements are reported as informational messages, containing the actual SQL statement being used. Dynamo wraps the Connection object to separate out SQL error, warning, info, and debug messages.

To view info messages, set the connection pool’s loggingSQLInfo property to true:

loggingSQLInfo=true

All calls to set values into a PreparedStatement or CallableStatement, or to read values from a ResultSet, are reported as debugging messages, containing the values set or read. To view these messages, set the connection pool’s loggingSQLDebug property to true:

loggingSQLDebug=true

All SQL exceptions are reported as errors. To view these errors, set the connection pool’s loggingSQLError property to true:

loggingSQLError=true

Because connections are monitored, the following properties are available to the JDBC connection pool:

Property Name

Description

Default Value

maxFieldSize

The size of the data that can be returned for any column

null

maxRows

The maximum number of rows that can be returned for any query

null

queryTimeout

The maximum number of seconds that the driver will wait for a statement to execute

null

initializingSQL

The array of SQL commands to be executed upon a Connection being created. Note that these commands can be used to set lock timeouts, set isolation levels, and test connections.

null

Note: When a monitored connection detects a SQL exception, the connection closes instead of being returned to the connection pool.

 
loading table of contents...