user manual

238 BES Developer’s Guide
Getting debug output
Getting debug output
A number of system properties can be set to log activity at datasource,
connection pool, connection and statement levels during application
processing. It is not necessary to configure these properties during normal
application runtime execution but should a situation arise where details of
JDBC flow of control is needed these options are useful. Runtime output
generated with these properties set can be provided to Borland Technical
Support to help resolve issues involving JDBC datasource and connections.
Descriptions of Borland Enterprise Server's pooled connection
states
When the EJB container's statistic gathering option is enabled, the Partition
event log contains useful statistics about the JDBC connections pool. The log
lists the number of connections in the various lifecycle states of a pooled
JDBC2 connection. Here follows a description of each state.
■
Free: a cached/pooled connection that is available for use by an application
■
TxBusy: a cached connection that is in use in a transaction
■
NoTxBusy: a cached connection that is in use by an application with no
transaction context
■
Committed: a connection that was associated with a transaction received
a commit() call from the transaction service
■
RolledBack: a connection that was associated with a transaction received
a rollback() call from the transaction service
System Property
Name Type Description Default
DataSourceDebug Boolean Report activity at
datasource level
for all datasources
False
ConnectionPoolDebug Boolean Report activity at
connection pool
level for all
datasources
False
ConnetionPoolStateD
ebug
Boolean Reports transitions
of connections in
connection pool
False
JDBCProxyDebug Boolean Report activity at
connection level for
all connections
False
PreparedStatementCa
cheDebug
Boolean Report activity at
prepared
statement level for
all statements
False