[ http://issues.apache.org/jira/browse/GERONIMO-1423?page=comments#action_12362135 ]
Aaron Mulder commented on GERONIMO-1423: ---------------------------------------- However, at a minimum, you need to either: 1) change the log configuration in var/log/server-log4j.properties instead of trying to use a properties file in WEB-INF/classes or 2) add <hidden-classes>org.apache.log4j</hidden-classes> to the deployment plan for your WAR or EAR to force your web application to use it's own Log4J settings and ignore the system-wide Log4j configuration. > log4j.properties's category is ignored > -------------------------------------- > > Key: GERONIMO-1423 > URL: http://issues.apache.org/jira/browse/GERONIMO-1423 > Project: Geronimo > Type: Bug > Components: Logging > Versions: 1.0 > Environment: JRE 1.5.0_06, Linux > Reporter: viewhero > Priority: Critical > Fix For: 1.0.1 > > log4j.properties that is included war file's WEB-INF/classes. > like this. > ------------------------------------------------------------------------------------------------------------------------------------------- > log4j.rootCategory=ERROR, A1 > log4j.appender.A1=org.apache.log4j.ConsoleAppender > log4j.appender.A1.layout=org.apache.log4j.PatternLayout > log4j.appender.A1.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p [%t] > (%F:%L) - %m%n > log4j.category.jp.ne.xxx=ERROR > ------------------------------------------------------------------------------------------------------------------------------------------- > but, INFO message was written to geronimo.log. > geronimo must read log4j.properties each web applications. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
