Ojdbc14_g.jar and tracing

Question

I have been trying to get tracing to work for the last couple of days. I have read all of the docs about tracing but I am still missing something. I am hoping that someone can fill in the gaps for me.
In my code JSP code I have the following:
System.setProperty("java.util.logging.config.file", "/pirusfj/OracleLog.properties");
oracle.jdbc.driver.OracleLog.setTrace(true);
System.out.println ("Tracing turned on");
Where in my web directories should the OracleLog.properties file be so that it is picked up by the logger? Do I need to have OracleHome set to that location? Also I have everything set to FINEST. Should the log out put come out as INFO: log message or FINEST: log message?
The OracleLog.properties file is the one that came with the demo code and everything is changed from INFO to FINEST. Here is a copy of it:
# OracleLog.properties Copyright Oracle 2004
# Controls output of OracleLog for JDBC applications using
# JDK1.4.x and ojdbc14_g.jar
# See the Javadoc for OracleLog for more information.
# Starting with Oracle 10gR1 the OracleLog system in
# ojdbc14_g.jar for JDK1.4.x uses the services of
# java.util.logging.* This file is a starting
# point for controlling that output via a properties
# file. Note that there is also a programatic interface
# for java.util.logging which may be used as well. That
# would allow finer grained control and the ability to
# change the logging as the program runs.
# Copy this file to your runtime directory to use as a
# starting point. You should expect to change it to
# suit your needs.
# To enable logging controlled by this file start your
# main java class with the swtiches
# -Doracle.jdbc.Trace=true
# -Djava.util.logging.config.file=OracleLog.properties
# See also the file logging.properties in the jre/lib directory
# in your JDK1.4 installation and the JDK documentation.
handlers= java.util.logging.ConsoleHandler
.level= FINEST
# default file output is in user's home directory.
java.util.logging.FileHandler.pattern = jdbc.log
java.util.logging.FileHandler.limit = 50000
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter
# Setting this to SEVERE avoids duplicate output from default logger
java.util.logging.ConsoleHandler.level = FINEST
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
# Starting point -- main driver function level log
oracle.jdbc.level = FINEST
oracle.jdbc.driver.level = FINEST
# Uncomment and/or change the levels for more detail
oracle.jdbc.datum.level = FINEST
oracle.jdbc.adt.level = FINEST
oracle.jdbc.conversion.level = FINEST
oracle.jdbc.adt.level = FINEST
oracle.jdbc.thin.level = FINEST
oracle.jdbc.datum.level = FINEST
oracle.jdbc.kprb.level = FINEST
oracle.jdbc.pool.level = FINEST
oracle.jdbc.xa.level = FINEST
oracle.jdbc.sqlj.level = FINEST
oracle.jdbc.oci.level = FINEST
oracle.jdbc.jpub.level = FINEST
# Category definitions are listed in the following:
# USER_OPER JDBC API level tracing.
# INFO (expected volume: low)
# PROG_ERR Program error (eg. an unexpected value encountered
# SEVERE in a switch statement). Messages of this category
# is not maskable.
# (expected volume: low)
# ERROR Error conditions that usually lead to catastrophic
# SEVERE or unrecoverable results. Messages of this
# category is not maskable.
# (expected volume: low)
# WARNING Error conditions that are usually recoverable.
# WARNING Note that the module and sub-module filters do not
# apply to messages of this category. See also
# enableWarning().
# (expected volume: low)
# FUNCTION Function entry/return information.
# FINE (expected volume: medium)
# DEBUG1 High-level debug information.
# FINER (expected volume: medium)
# DEBUG2 Detail debug information.
# FINEST (expected volume: high)
# SQL_STR SQL string
# CONFIG (expected volume: low)
Any help would be greatly appreciated.
Thanks,
Susan Conger

Answer 1

Duplicate post:
ojdbc14_g.jar and tracing
Susan,
You wrote:
In my JSP code I have the following:
System.setProperty("java.util.logging.config.file", "/pirusfj/OracleLog.properties");For some "System" properties, the "setProperty()" method does nothing.
These properties must be set on the command-line using the "-D" option of the "java" command.
Indeed, this is stated in the comments of the demo code that you posted, namely:
# -Djava.util.logging.config.file=OracleLog.propertiesYou also asked:
Where in my web directories should the OracleLog.properties file beThat may depend on the JSP engine you are using.
Excuse me, but I couldn't find that information in your post.
Hence I can't really answer that question.
Good Luck,
Avi.