I just upgraded from b2 to b3 and since then Log4j (1.2.6) is acting strangelly: it ignores the settings and sends everything on stderr.
Here's the log4j.properties (the interesing part): #log4j.rootLogger=WARN, A1 log4j.logger.com.mycompany=DEBUG, A1 log4j.logger.JBO=WARN, JBO log4j.logger.org.apache=WARN, A1 log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender log4j.appender.A1.File=Project.log log4j.appender.A1.DatePattern='.'yyyy-MM-dd ########################## # Request logger log4j.logger.RequestLogger=INFO, REQ1 log4j.appender.REQ1=org.apache.log4j.DailyRollingFileAppender log4j.appender.REQ1.File=Project.request.log log4j.appender.REQ1.DatePattern='.'yyyy-MM-dd ########################## # Oracle JBO log4j.appender.JBO=org.apache.log4j.DailyRollingFileAppender log4j.appender.JBO.File=oracle.jbo.trace.log log4j.appender.JBO.DatePattern='.'yyyy-MM-dd All the categories are covered by their specific loggers (com.mycompany, org.apache etc) so I don't need the rootLogger. However, when added (associated with A1) everything actually goes to A1 (Project.log file) and not to stderr but the correct files are empty. This might be the commons-logging.jar issue (while upgrading, I copied all the libraries, including struts.jar and commons-logging.jar to my WEB-INF/lib dir). Anyone? With struts-b2 (and the corresponding commons- libraries) everything was quite nice. I'm using WSAD 4.0.3 and its WebSphere test environment (which is actually WAS 4.0.2 AES, so servlet spec. 2.2), jdk 1.3.1, log4j 1.2.6. Thanks. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
