You can use DataDirect Spy to track JDBC calls made by a running application with either of these features:
JNDI for Naming Databases
Connection Pooling
Java Transaction API (JTA)
Note: JTA is currently only supported by the following 6.0 drivers: Oracle and SQL Server drivers.
You can use DataDirect Spy to track JDBC calls made by a running application with any of these features. The com.ddtek.jdbcx.Oracle.OracleDataSource class supports setting a semi-colon separated list of DataDirect Spy attributes. For more information about configuring data sources, refer to the user’s guide for your driver.
Windows example
The following example creates a JDBC data source for the Oracle driver, which enables DataDirect Spy.
Note: If coding a path on Windows to the log file in a Java string, the backslash character (\) must be preceded by the Java escape character, a backslash. For example: log=(file)C:\\temp\\spy.log;logIS=yes;logTName=yes.
DataDirect Spy loads the driver and logs all JDBC activity to the spy.log file located in the C:\temp directory (log=(file)C:\\temp\\spy.log). In addition to regular JDBC activity, the spy.log file also logs activity on InputStream and Reader objects (logIS=yes). It also includes the name of the current thread (logTName=yes).
UNIX example
The following example creates a JDBC data source for the Oracle driver, which enables DataDirect Spy.
DataDirect Spy loads the driver and logs all JDBC activity to the spy.log file located in the /tmp directory (log=(file)/tmp/spy.log). In addition to regular JDBC activity, the spy.log file also logs activity on InputStream and Reader objects (logIS=yes). It also includes the name of the current thread (logTName=yes).