Vic,
The defects can be reproduced easily.
Assuming you deployed your application on Tomcat, the combination known to work safely is:
1) Leave the file TOMCAT_HOME/bin/commons-logging-api.jar as is.
2) Place the files commons-logging.jar and log4j.jar in the directory TOMCAT_HOME/commons/lib/.
3) Do not include any other copies of commons-logging.jar and log4j.jar in your web-applications' WEB-INF/lib/ directory.
4) Do not set the org.apache.commons.logging.LogFactory property.
Was your deployment combination different from the above?
At 02:54 PM 2/18/2005, Vic wrote:
I used to use both together. For what ever reason, I have stress tested and put in production several systems, one with 10,000 concurrent users, one w/ 40,000 concurrent users... and everything seems to be working. I was not aware of any bugs.
Now .... I use WebStart so likely at least a part will be JDK logging. .V
Ceki Gülcü wrote:
a problem with JCL, a totally defective piece of software, which makes life very difficult, if not impossible, for log4j users.
-- Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
