Just to finish up this thread, I found that the root cause of my problems
was that I had a commons-logging.properties file buried in another jar file
that redirected logging to a logger that wasn't able to be initialized.
Kinda a catch-22. Anyway, thanks for the help.
Ben
On 10/25/06, Ben
I'm trying to move an existing app I had running in Websphere 6 over to
Tomcat 5.5.20. My development platform is WinXP. As part of this
migration, I'm relying on the log files to help me determine what's
happening.
I haven't modified the logging stuff whatsoever. This is what I get in
According to http://tomcat.apache.org/tomcat-5.5-doc/logging.html, A
handler's log level threshold can be set using SEVERE, CONFIG, INFO,
WARN, FINE, FINEST or ALL. The logging.properties shipped with JDK
is set to INFO. For kicks, I did try setting everything to DEBUG
which didn't hav any
