Red Hat Application Server, Manual

Page: 61 / 296

Chapter 4. Configuring JDBC DataSources 53
•
rdb.postgres: mapper for PostgreSQL
•
rdb.oracle8: mapper for Oracle 8 and lesser versions
•
rdb.oracle: mapper for Oracle 9
•
rdb.mysql: mapper for MySQL
4.3. ConnectionManager Configuration
Each Datasource is implemented as a connection manager that can be configured via some additional
properties described in the following table. Refer to the
Oracle1.properties
file to see an example
of settings. All these settings have default values and are not required.
Property Name Description Default Value
jdbc.connchecklevel JDBC connection checking
level: 0 (no check), 1 (check
connection), higher (call the
test statement)
1
jdbc.connmaxage maximum age for jdbc
connections
30 minutes
jdbc.connteststmt test statement select 1
jdbc.minconpool Minimum number of
connections in the pool
0
jdbc.maxconpool Maximum number of
connections in the pool
-1 (no max boundary)
jdbc.connteststmt
is not used when
jdbc.connchecklevel
is equal to
0
or
1
.
jdbc.minconpool
is used at DataSource creation time. Modifying this property during runtime has
no effect on already-created DataSources.
jdbc.maxconpool
can be dynamically increased or decreased.
4.4. Tracing SQL Requests Through P6Spy
The P6Spy tool is integrated within JOnAS to provide a means for easily tracing the SQL requests
that are sent to the database (see http://www.p6spy.com/).
To enable this tracing feature, perform the following configuration steps:
1. Set the
datasource.classname
property of your DataSource properties file to
com.p6spy.engine.spy.P6SpyDriver
2. Set the
realdriver
property in the
spy.properties
file (located within
$JONAS_BASE/conf
) to the JDBC driver of your actual database
3. Verify that
logger.org.objectweb.jonas.jdbc.sql.level
is set to
DEBUG
in the
$JONAS_BASE/conf/trace.properties
file.
Example:
DataSource properties file contents:
datasource.name jdbc_3
datasource.url jdbc:postgresql://your_host:port/your_db