Is there a way to turn off additivity in the configuration instead of in code via Category.setAdditivity(false)?
-----Original Message----- From: Ceki G�lc� [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 26, 2004 10:11 AM To: Log4J Users List Subject: Re: Attempted to append to closed appender At 03:57 PM 10/26/2004, you wrote: >I searched and found a couple threads on this @ Mail Archive, but those >configurations were via XML and we are using log4j.properties. >Same problem as other people, once we change/add a level on the fly, our >app server log starts filling up with >log4j:ERROR Attempted to append to closed appender named [debug] >entries. > ># Set root category priority to DEBUG and its only appender to A1. >log4j.rootLogger=INFO, file, toolkit >log4j.category.org=ERROR, file >log4j.category.jsp_servlet=INFO, toolkit, debug The problem might be linked to the fact that you are attaching an appender named "debug" to several loggers (aka categories). You probably do not want to do that because of the appender additivity rule. -- Ceki G�lc� For log4j documentation consider "The complete log4j manual" http://www.qos.ch/shop/products/eclm/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
