Bug report for Log4j [2003/12/21]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 4561|Ass|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 5211|Ass|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 7678|Opn|Nor|2002-04-02|if log file is deleted, data will be lost until de| | 7948|Opn|Nor|2002-04-11|Layout & Subclasses: getFooter never called | | 8529|New|Maj|2002-04-25|JDBCAppender doesn't take throwable stack trace | | 9150|New|Maj|2002-05-16|No check in FileAppender if parent-path exists| |10560|New|Nor|2002-07-08|DailyRollingAppender does not roll each period| |10587|New|Enh|2002-07-09|Illogical difference between removeAppender and re| |11009|New|Min|2002-07-20|Cannot access XMLSample page | |11142|New|Min|2002-07-24|org.apache.log4j.net.SocketServer doesn't work wit| |11186|New|Min|2002-07-25|DefaultRenderer.doRender() does not handle NullPoi| |11285|New|Nor|2002-07-30|SocketAppender fails to reconnect immediately | |11446|New|Nor|2002-08-03|Rolling, DailyRolling & FileAppender do not append| |11474|New|Enh|2002-08-05|Improvements to rolling file appenders| |11512|New|Nor|2002-08-06|Chainsaw forces output of its internal messages to| |11907|New|Enh|2002-08-21|DailyRollingFileAppender should extend RollingFile| |12112|New|Maj|2002-08-28|CountingQuietWriter wrongly uses # of characters i| |13021|New|Min|2002-09-26|DailyRollingFileAppender - change renameTo| |13099|New|Nor|2002-09-27|DOMConfigurator ignores category factory setting | |13171|New|Enh|2002-10-01|Some little spelling mistakes and deprecation warn| |13540|New|Nor|2002-10-11|log factor 5 max record memory overflow possible | |13659|New|Nor|2002-10-15|NTEventLogAppender event categories and usernames | |13702|New|Enh|2002-10-16|More options when naming log files using DailyRoll| |13900|New|Nor|2002-10-23|SMTPAppender doesn't use fallback append. for emai| |13947|New|Enh|2002-10-24|Change DailyRollingFileAppender.rollover() to prot| |14198|New|Nor|2002-11-03|jni error when running againt Sun JRE 1.4.0_02 wi| |14350|New|Nor|2002-11-07|Patch to substitute variables in the log4j.configu| |14435|New|Enh|2002-11-11|Right-truncate priority to 1 character| |14551|New|Nor|2002-11-14|missing or displaced dtd for XMLayout class | |14934|New|Nor|2002-11-28|MDC has no setContext() method| |14935|New|Nor|2002-11-28|Logger.getLogger()| |15056|New|Maj|2002-12-04|DailyRollingFileAppender doesn't roll over weeks, | |15177|New|Nor|2002-12-09|configureAndWatch fails with ExternallyRolledFileA| |15198|New|Nor|2002-12-09|TelnetAppender: NullPointerException if SocketHand| |15501|New|Nor|2002-12-18|FallbackErrorHandler throws NPW if no loggers are | |15585|New|Maj|2002-12-20|log4j does not show Class Name, Method, or Line Nu| |15867|New|Nor|2003-01-07|compile error in VisalAge For Java after import | |15885|New|Maj|2003-01-08|EXCEPTION_ACCESS_VIOLATION with a particular Conve| |15896|New|Nor|2003-01-08|PropertyConfigurator.configureAndWatch thread not | |15899|New|Enh|2003-01-08|SocketServer won't use IP address if server has no| |15942|New|Nor|2003-01-10|Can't specify encoding to ConsoleAppender | |15960|New|Nor|2003-01-10|TelnetAppender prevents tomcat from shutting down | |16022|New|Enh|2003-01-13|ObjectRenderers should also apply to l7dlog | |16105|New|Nor|2003-01-15|AsyncAppender with null message | |16229|New|Enh|2003-01-17|Convenience methods to cut object allocations in a| |16238|New|Cri|2003-01-19|log4j(1.2.6) - does not terminate if permission is| |16280|New|Min|2003-01-21|Error Message a
Bug report for Log4j [2002/02/25]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal EHN=Ehnancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 1459|New|Enh|2001-04-23|RollingFileAppender: keep unlimited number of back| | 1553|Ass|Enh|2001-04-27|A couple of documentation improvements| | 1669|Opn|Nor|2001-05-08|Logging 200,000 events in rapid sequence causes As| | 1960|Ass|Nor|2001-06-01|Extending the standard layout class and implementi| | 2246|New|Enh|2001-06-20|Throwable indentation & improving String escapeHTM| | 2251|New|Enh|2001-06-20|org.apache.log4j.helpers.OptionConverter's referen| | 2276|New|Nor|2001-06-21|stack trace of the exception is not getting logged| | 2287|New|Enh|2001-06-22|Hierarchy.disable package scoped | | 2341|Ass|Enh|2001-06-26|FileAppender should explicitly buffer output? | | 2370|Ass|Enh|2001-06-27|Rewrite PatternTest to use JUnit | | 2377|Ass|Blk|2001-06-28|A java.lang.ExceptionInInitializerError is thrown | | 2383|New|Nor|2001-06-28|BasicConfigurator's deprecated method : enableAll(| | 2498|New|Nor|2001-07-07|WriterAppender doesn't flush footer output| | 2558|Ass|Enh|2001-07-10|FileAppender requires / for proper useage.| | 2586|New|Nor|2001-07-11|Netscpe JRE-Plugin SSL BeanInfo not found problem | | 2686|New|Enh|2001-07-19|DailyRollingFileAppender with max file size | | 2690|New|Nor|2001-07-19|DOMConfigurator cannot be compiled (org.w3c) | | 2701|New|Blk|2001-07-19|WriterAppender does not allow logging with other c| | 2726|New|Min|2001-07-21|[doc bug] incorrect explanation of priority level | | 2791|New|Enh|2001-07-25|RollingFileAppender should provide a rollover() on| | 2953|New|Maj|2001-08-01|RollingFileAppender loses log files | | 2976|New|Nor|2001-08-03|Defaultvalues in properties during configuration n| | 3008|New|Nor|2001-08-06|Log4j stopped rolling log while program was runnin| | 3023|New|Min|2001-08-07|Documentation change - JUnit version dependency | | 3058|Ass|Nor|2001-08-09|DOMConfigurator File Sharing Access log4j.dtd | | 3071|New|Min|2001-08-09|syntax error in explanatory java code | | 3091|New|Cri|2001-08-10|computeCheckPeriod() doesn't work.| | 3105|New|Nor|2001-08-13|DailyRollingFileAppender not working correctly on | | 3163|New|Enh|2001-08-19|ServletLogAppender contrib| | 3607|New|Maj|2001-09-14|(log4j 1.1.3) RollingFileAppenderBeanInfo will not| | 3610|New|Nor|2001-09-14|The XPriority example is incorrect| | 3786|New|Enh|2001-09-23|Add Category.getInstance() variant that finds clas| | 3794|New|Nor|2001-09-24|TRACE priority(i.e. priority lower than DEBUG) in| | 3853|New|Min|2001-09-27|Javadoc. BasicConfigurator.configure() uses Consol| | 3915|New|Nor|2001-10-02|AsyncAppender "eats" location information | | 3933|New|Maj|2001-10-02|SocketServer Poor Performance could be improved si| | 4024|New|Nor|2001-10-08|Configuration of the Source of NTEventLogAppender | | 4090|New|Maj|2001-10-11|DailyRollingFileAppender loses logged data| | 4098|New|Enh|2001-10-11|Setting name for the FileWatchdog thread | | 4106|New|Nor|2001-10-11|DOM Configurator doesn't parse filename and line n| | 4122|New|Nor|2001-10-12|variable substitution doesn't support recursive su| | 4301|New|Cri|2001-10-19|Category.getInstance(String, CategoryFactory) retu| | 4378|New|Min|2001-10-23|Misspelled word in FAQ| | 4561|New|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4746|New|Nor|2001-11-08|NTAppender does not use the layout speciifed in th| | 4756|New|Enh|2001-11-08|Add controls to NT Event Log appender for event #,| | 4802|New|Cri|2001-11-11|Not Serializable in Log4J 1.1.3 | | 4815|New|Nor|2001-11-12|P
Bug report for Log4j [2002/03/03]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal EHN=Ehnancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 1459|New|Enh|2001-04-23|RollingFileAppender: keep unlimited number of back| | 1553|Ass|Enh|2001-04-27|A couple of documentation improvements| | 1669|Opn|Nor|2001-05-08|Logging 200,000 events in rapid sequence causes As| | 1960|Ass|Nor|2001-06-01|Extending the standard layout class and implementi| | 2246|New|Enh|2001-06-20|Throwable indentation & improving String escapeHTM| | 2251|New|Enh|2001-06-20|org.apache.log4j.helpers.OptionConverter's referen| | 2276|New|Nor|2001-06-21|stack trace of the exception is not getting logged| | 2287|New|Enh|2001-06-22|Hierarchy.disable package scoped | | 2341|Ass|Enh|2001-06-26|FileAppender should explicitly buffer output? | | 2370|Ass|Enh|2001-06-27|Rewrite PatternTest to use JUnit | | 2377|Ass|Blk|2001-06-28|A java.lang.ExceptionInInitializerError is thrown | | 2383|New|Nor|2001-06-28|BasicConfigurator's deprecated method : enableAll(| | 2498|New|Nor|2001-07-07|WriterAppender doesn't flush footer output| | 2558|Ass|Enh|2001-07-10|FileAppender requires / for proper useage.| | 2586|New|Nor|2001-07-11|Netscpe JRE-Plugin SSL BeanInfo not found problem | | 2686|New|Enh|2001-07-19|DailyRollingFileAppender with max file size | | 2690|New|Nor|2001-07-19|DOMConfigurator cannot be compiled (org.w3c) | | 2701|New|Blk|2001-07-19|WriterAppender does not allow logging with other c| | 2726|New|Min|2001-07-21|[doc bug] incorrect explanation of priority level | | 2791|New|Enh|2001-07-25|RollingFileAppender should provide a rollover() on| | 2953|New|Maj|2001-08-01|RollingFileAppender loses log files | | 2976|New|Nor|2001-08-03|Defaultvalues in properties during configuration n| | 3008|New|Nor|2001-08-06|Log4j stopped rolling log while program was runnin| | 3023|New|Min|2001-08-07|Documentation change - JUnit version dependency | | 3058|Ass|Nor|2001-08-09|DOMConfigurator File Sharing Access log4j.dtd | | 3071|New|Min|2001-08-09|syntax error in explanatory java code | | 3091|New|Cri|2001-08-10|computeCheckPeriod() doesn't work.| | 3105|New|Nor|2001-08-13|DailyRollingFileAppender not working correctly on | | 3163|New|Enh|2001-08-19|ServletLogAppender contrib| | 3607|New|Maj|2001-09-14|(log4j 1.1.3) RollingFileAppenderBeanInfo will not| | 3610|New|Nor|2001-09-14|The XPriority example is incorrect| | 3786|New|Enh|2001-09-23|Add Category.getInstance() variant that finds clas| | 3794|New|Nor|2001-09-24|TRACE priority(i.e. priority lower than DEBUG) in| | 3853|New|Min|2001-09-27|Javadoc. BasicConfigurator.configure() uses Consol| | 3915|New|Nor|2001-10-02|AsyncAppender "eats" location information | | 3933|New|Maj|2001-10-02|SocketServer Poor Performance could be improved si| | 4024|New|Nor|2001-10-08|Configuration of the Source of NTEventLogAppender | | 4090|New|Maj|2001-10-11|DailyRollingFileAppender loses logged data| | 4098|New|Enh|2001-10-11|Setting name for the FileWatchdog thread | | 4106|New|Nor|2001-10-11|DOM Configurator doesn't parse filename and line n| | 4122|New|Nor|2001-10-12|variable substitution doesn't support recursive su| | 4301|New|Cri|2001-10-19|Category.getInstance(String, CategoryFactory) retu| | 4378|New|Min|2001-10-23|Misspelled word in FAQ| | 4561|New|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4746|New|Nor|2001-11-08|NTAppender does not use the layout speciifed in th| | 4756|New|Enh|2001-11-08|Add controls to NT Event Log appender for event #,| | 4802|New|Cri|2001-11-11|Not Serializable in Log4J 1.1.3 | | 4815|New|Nor|2001-11-12|P
Bug report for Log4j [2002/03/10]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal EHN=Ehnancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 1459|New|Enh|2001-04-23|RollingFileAppender: keep unlimited number of back| | 1553|Ass|Enh|2001-04-27|A couple of documentation improvements| | 1669|Opn|Nor|2001-05-08|Logging 200,000 events in rapid sequence causes As| | 1960|Ass|Nor|2001-06-01|Extending the standard layout class and implementi| | 2246|New|Enh|2001-06-20|Throwable indentation & improving String escapeHTM| | 2251|New|Enh|2001-06-20|org.apache.log4j.helpers.OptionConverter's referen| | 2276|New|Nor|2001-06-21|stack trace of the exception is not getting logged| | 2287|New|Enh|2001-06-22|Hierarchy.disable package scoped | | 2341|Ass|Enh|2001-06-26|FileAppender should explicitly buffer output? | | 2370|Ass|Enh|2001-06-27|Rewrite PatternTest to use JUnit | | 2377|Ass|Blk|2001-06-28|A java.lang.ExceptionInInitializerError is thrown | | 2383|New|Nor|2001-06-28|BasicConfigurator's deprecated method : enableAll(| | 2498|New|Nor|2001-07-07|WriterAppender doesn't flush footer output| | 2558|Ass|Enh|2001-07-10|FileAppender requires / for proper useage.| | 2586|New|Nor|2001-07-11|Netscpe JRE-Plugin SSL BeanInfo not found problem | | 2686|New|Enh|2001-07-19|DailyRollingFileAppender with max file size | | 2690|New|Nor|2001-07-19|DOMConfigurator cannot be compiled (org.w3c) | | 2701|New|Blk|2001-07-19|WriterAppender does not allow logging with other c| | 2726|New|Min|2001-07-21|[doc bug] incorrect explanation of priority level | | 2791|New|Enh|2001-07-25|RollingFileAppender should provide a rollover() on| | 2953|New|Maj|2001-08-01|RollingFileAppender loses log files | | 2976|New|Nor|2001-08-03|Defaultvalues in properties during configuration n| | 3008|New|Nor|2001-08-06|Log4j stopped rolling log while program was runnin| | 3023|New|Min|2001-08-07|Documentation change - JUnit version dependency | | 3058|Ass|Nor|2001-08-09|DOMConfigurator File Sharing Access log4j.dtd | | 3071|New|Min|2001-08-09|syntax error in explanatory java code | | 3091|New|Cri|2001-08-10|computeCheckPeriod() doesn't work.| | 3105|New|Nor|2001-08-13|DailyRollingFileAppender not working correctly on | | 3163|New|Enh|2001-08-19|ServletLogAppender contrib| | 3607|New|Maj|2001-09-14|(log4j 1.1.3) RollingFileAppenderBeanInfo will not| | 3610|New|Nor|2001-09-14|The XPriority example is incorrect| | 3786|New|Enh|2001-09-23|Add Category.getInstance() variant that finds clas| | 3794|New|Nor|2001-09-24|TRACE priority(i.e. priority lower than DEBUG) in| | 3853|New|Min|2001-09-27|Javadoc. BasicConfigurator.configure() uses Consol| | 3915|New|Nor|2001-10-02|AsyncAppender "eats" location information | | 3933|New|Maj|2001-10-02|SocketServer Poor Performance could be improved si| | 4024|New|Nor|2001-10-08|Configuration of the Source of NTEventLogAppender | | 4090|New|Maj|2001-10-11|DailyRollingFileAppender loses logged data| | 4098|New|Enh|2001-10-11|Setting name for the FileWatchdog thread | | 4106|New|Nor|2001-10-11|DOM Configurator doesn't parse filename and line n| | 4122|New|Nor|2001-10-12|variable substitution doesn't support recursive su| | 4301|New|Cri|2001-10-19|Category.getInstance(String, CategoryFactory) retu| | 4378|New|Min|2001-10-23|Misspelled word in FAQ| | 4561|New|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4746|New|Nor|2001-11-08|NTAppender does not use the layout speciifed in th| | 4756|New|Enh|2001-11-08|Add controls to NT Event Log appender for event #,| | 4802|New|Cri|2001-11-11|Not Serializable in Log4J 1.1.3 | | 4815|New|Nor|2001-11-12|P
Bug report for Log4j [2002/03/17]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal EHN=Ehnancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 1459|New|Enh|2001-04-23|RollingFileAppender: keep unlimited number of back| | 1553|Ass|Enh|2001-04-27|A couple of documentation improvements| | 1669|Opn|Nor|2001-05-08|Logging 200,000 events in rapid sequence causes As| | 1960|Ass|Nor|2001-06-01|Extending the standard layout class and implementi| | 2246|New|Enh|2001-06-20|Throwable indentation & improving String escapeHTM| | 2251|New|Enh|2001-06-20|org.apache.log4j.helpers.OptionConverter's referen| | 2276|New|Nor|2001-06-21|stack trace of the exception is not getting logged| | 2377|Ass|Blk|2001-06-28|A java.lang.ExceptionInInitializerError is thrown | | 2383|New|Nor|2001-06-28|BasicConfigurator's deprecated method : enableAll(| | 2498|New|Nor|2001-07-07|WriterAppender doesn't flush footer output| | 2586|New|Nor|2001-07-11|Netscpe JRE-Plugin SSL BeanInfo not found problem | | 2686|New|Enh|2001-07-19|DailyRollingFileAppender with max file size | | 2690|New|Nor|2001-07-19|DOMConfigurator cannot be compiled (org.w3c) | | 2701|New|Blk|2001-07-19|WriterAppender does not allow logging with other c| | 2726|New|Min|2001-07-21|[doc bug] incorrect explanation of priority level | | 2791|New|Enh|2001-07-25|RollingFileAppender should provide a rollover() on| | 2953|New|Maj|2001-08-01|RollingFileAppender loses log files | | 2976|New|Nor|2001-08-03|Defaultvalues in properties during configuration n| | 3008|New|Nor|2001-08-06|Log4j stopped rolling log while program was runnin| | 3023|New|Min|2001-08-07|Documentation change - JUnit version dependency | | 3058|Ass|Nor|2001-08-09|DOMConfigurator File Sharing Access log4j.dtd | | 3071|New|Min|2001-08-09|syntax error in explanatory java code | | 3105|New|Nor|2001-08-13|DailyRollingFileAppender not working correctly on | | 3607|New|Maj|2001-09-14|(log4j 1.1.3) RollingFileAppenderBeanInfo will not| | 3610|New|Nor|2001-09-14|The XPriority example is incorrect| | 3794|New|Nor|2001-09-24|TRACE priority(i.e. priority lower than DEBUG) in| | 3853|New|Min|2001-09-27|Javadoc. BasicConfigurator.configure() uses Consol| | 3915|New|Nor|2001-10-02|AsyncAppender "eats" location information | | 3933|New|Maj|2001-10-02|SocketServer Poor Performance could be improved si| | 4024|New|Nor|2001-10-08|Configuration of the Source of NTEventLogAppender | | 4090|New|Maj|2001-10-11|DailyRollingFileAppender loses logged data| | 4098|New|Enh|2001-10-11|Setting name for the FileWatchdog thread | | 4106|New|Nor|2001-10-11|DOM Configurator doesn't parse filename and line n| | 4122|New|Nor|2001-10-12|variable substitution doesn't support recursive su| | 4378|New|Min|2001-10-23|Misspelled word in FAQ| | 4561|New|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4746|New|Nor|2001-11-08|NTAppender does not use the layout speciifed in th| | 4756|New|Enh|2001-11-08|Add controls to NT Event Log appender for event #,| | 4802|New|Cri|2001-11-11|Not Serializable in Log4J 1.1.3 | | 4815|New|Nor|2001-11-12|PropertySetter ignores default properties in the j| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 4913|New|Min|2001-11-16|org.apache.log4j.helpers.FileWatchdog should allow| | 4979|New|Nor|2001-11-20|Docs issue and .ZIP missing files.| | 5211|New|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5232|New|Nor|2001-12-02|DOMConfigurator does not parse appenders if invoke| | 5393|New|Maj|2001-12-12|DailyRollingFileAppender should have rolling for n| | 5444|New|Nor|2001-12-15|AsyncAppender throws NullPointerException | | 5485|New|Nor|2001-12-18|XMLLay
Bug report for Log4j [2002/03/24]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal EHN=Ehnancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 1459|New|Enh|2001-04-23|RollingFileAppender: keep unlimited number of back| | 1553|Ass|Enh|2001-04-27|A couple of documentation improvements| | 1669|Opn|Nor|2001-05-08|Logging 200,000 events in rapid sequence causes As| | 1960|Ass|Nor|2001-06-01|Extending the standard layout class and implementi| | 2246|New|Enh|2001-06-20|Throwable indentation & improving String escapeHTM| | 2251|New|Enh|2001-06-20|org.apache.log4j.helpers.OptionConverter's referen| | 2276|New|Nor|2001-06-21|stack trace of the exception is not getting logged| | 2377|Ass|Blk|2001-06-28|A java.lang.ExceptionInInitializerError is thrown | | 2383|New|Nor|2001-06-28|BasicConfigurator's deprecated method : enableAll(| | 2498|New|Nor|2001-07-07|WriterAppender doesn't flush footer output| | 2586|New|Nor|2001-07-11|Netscpe JRE-Plugin SSL BeanInfo not found problem | | 2686|New|Enh|2001-07-19|DailyRollingFileAppender with max file size | | 2690|New|Nor|2001-07-19|DOMConfigurator cannot be compiled (org.w3c) | | 2701|New|Blk|2001-07-19|WriterAppender does not allow logging with other c| | 2726|New|Min|2001-07-21|[doc bug] incorrect explanation of priority level | | 2791|New|Enh|2001-07-25|RollingFileAppender should provide a rollover() on| | 2953|New|Maj|2001-08-01|RollingFileAppender loses log files | | 2976|New|Nor|2001-08-03|Defaultvalues in properties during configuration n| | 3008|New|Nor|2001-08-06|Log4j stopped rolling log while program was runnin| | 3023|New|Min|2001-08-07|Documentation change - JUnit version dependency | | 3058|Ass|Nor|2001-08-09|DOMConfigurator File Sharing Access log4j.dtd | | 3071|New|Min|2001-08-09|syntax error in explanatory java code | | 3105|New|Nor|2001-08-13|DailyRollingFileAppender not working correctly on | | 3607|New|Maj|2001-09-14|(log4j 1.1.3) RollingFileAppenderBeanInfo will not| | 3610|New|Nor|2001-09-14|The XPriority example is incorrect| | 3794|New|Nor|2001-09-24|TRACE priority(i.e. priority lower than DEBUG) in| | 3853|New|Min|2001-09-27|Javadoc. BasicConfigurator.configure() uses Consol| | 3915|New|Nor|2001-10-02|AsyncAppender "eats" location information | | 3933|New|Maj|2001-10-02|SocketServer Poor Performance could be improved si| | 4024|New|Nor|2001-10-08|Configuration of the Source of NTEventLogAppender | | 4090|New|Maj|2001-10-11|DailyRollingFileAppender loses logged data| | 4098|New|Enh|2001-10-11|Setting name for the FileWatchdog thread | | 4106|New|Nor|2001-10-11|DOM Configurator doesn't parse filename and line n| | 4122|New|Nor|2001-10-12|variable substitution doesn't support recursive su| | 4378|New|Min|2001-10-23|Misspelled word in FAQ| | 4561|New|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4746|New|Nor|2001-11-08|NTAppender does not use the layout speciifed in th| | 4756|New|Enh|2001-11-08|Add controls to NT Event Log appender for event #,| | 4802|New|Cri|2001-11-11|Not Serializable in Log4J 1.1.3 | | 4815|New|Nor|2001-11-12|PropertySetter ignores default properties in the j| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 4913|New|Min|2001-11-16|org.apache.log4j.helpers.FileWatchdog should allow| | 4979|New|Nor|2001-11-20|Docs issue and .ZIP missing files.| | 5211|New|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5232|New|Nor|2001-12-02|DOMConfigurator does not parse appenders if invoke| | 5393|New|Maj|2001-12-12|DailyRollingFileAppender should have rolling for n| | 5444|New|Nor|2001-12-15|AsyncAppender throws NullPointerException | | 5485|New|Nor|2001-12-18|XMLLay
Bug report for Log4j [2002/03/31]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 1459|New|Enh|2001-04-23|RollingFileAppender: keep unlimited number of back| | 1553|Ass|Enh|2001-04-27|A couple of documentation improvements| | 1669|Opn|Nor|2001-05-08|Logging 200,000 events in rapid sequence causes As| | 1960|Ass|Nor|2001-06-01|Extending the standard layout class and implementi| | 2246|New|Enh|2001-06-20|Throwable indentation & improving String escapeHTM| | 2251|New|Enh|2001-06-20|org.apache.log4j.helpers.OptionConverter's referen| | 2276|New|Nor|2001-06-21|stack trace of the exception is not getting logged| | 2377|Ass|Blk|2001-06-28|A java.lang.ExceptionInInitializerError is thrown | | 2383|New|Nor|2001-06-28|BasicConfigurator's deprecated method : enableAll(| | 2498|New|Nor|2001-07-07|WriterAppender doesn't flush footer output| | 2586|New|Nor|2001-07-11|Netscpe JRE-Plugin SSL BeanInfo not found problem | | 2686|New|Enh|2001-07-19|DailyRollingFileAppender with max file size | | 2690|New|Nor|2001-07-19|DOMConfigurator cannot be compiled (org.w3c) | | 2701|New|Blk|2001-07-19|WriterAppender does not allow logging with other c| | 2726|New|Min|2001-07-21|[doc bug] incorrect explanation of priority level | | 2791|New|Enh|2001-07-25|RollingFileAppender should provide a rollover() on| | 2953|New|Maj|2001-08-01|RollingFileAppender loses log files | | 2976|New|Nor|2001-08-03|Defaultvalues in properties during configuration n| | 3008|New|Nor|2001-08-06|Log4j stopped rolling log while program was runnin| | 3023|New|Min|2001-08-07|Documentation change - JUnit version dependency | | 3058|Ass|Nor|2001-08-09|DOMConfigurator File Sharing Access log4j.dtd | | 3071|New|Min|2001-08-09|syntax error in explanatory java code | | 3105|New|Nor|2001-08-13|DailyRollingFileAppender not working correctly on | | 3607|New|Maj|2001-09-14|(log4j 1.1.3) RollingFileAppenderBeanInfo will not| | 3610|New|Nor|2001-09-14|The XPriority example is incorrect| | 3794|New|Nor|2001-09-24|TRACE priority(i.e. priority lower than DEBUG) in| | 3853|New|Min|2001-09-27|Javadoc. BasicConfigurator.configure() uses Consol| | 3915|New|Nor|2001-10-02|AsyncAppender "eats" location information | | 3933|New|Maj|2001-10-02|SocketServer Poor Performance could be improved si| | 4024|New|Nor|2001-10-08|Configuration of the Source of NTEventLogAppender | | 4090|New|Maj|2001-10-11|DailyRollingFileAppender loses logged data| | 4098|New|Enh|2001-10-11|Setting name for the FileWatchdog thread | | 4106|New|Nor|2001-10-11|DOM Configurator doesn't parse filename and line n| | 4122|New|Nor|2001-10-12|variable substitution doesn't support recursive su| | 4378|New|Min|2001-10-23|Misspelled word in FAQ| | 4561|New|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4746|New|Nor|2001-11-08|NTAppender does not use the layout speciifed in th| | 4756|New|Enh|2001-11-08|Add controls to NT Event Log appender for event #,| | 4802|New|Cri|2001-11-11|Not Serializable in Log4J 1.1.3 | | 4815|New|Nor|2001-11-12|PropertySetter ignores default properties in the j| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 4913|New|Min|2001-11-16|org.apache.log4j.helpers.FileWatchdog should allow| | 4979|New|Nor|2001-11-20|Docs issue and .ZIP missing files.| | 5211|New|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5232|New|Nor|2001-12-02|DOMConfigurator does not parse appenders if invoke| | 5393|New|Maj|2001-12-12|DailyRollingFileAppender should have rolling for n| | 5444|New|Nor|2001-12-15|AsyncAppender throws NullPointerException | | 5485|New|Nor|2001-12-18|XMLLay
Bug report for Log4j [2002/04/07]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 1459|New|Enh|2001-04-23|RollingFileAppender: keep unlimited number of back| | 1553|Ass|Enh|2001-04-27|A couple of documentation improvements| | 1669|Opn|Nor|2001-05-08|Logging 200,000 events in rapid sequence causes As| | 1960|Ass|Nor|2001-06-01|Extending the standard layout class and implementi| | 2246|New|Enh|2001-06-20|Throwable indentation & improving String escapeHTM| | 2251|New|Enh|2001-06-20|org.apache.log4j.helpers.OptionConverter's referen| | 2276|New|Nor|2001-06-21|stack trace of the exception is not getting logged| | 2377|Ass|Blk|2001-06-28|A java.lang.ExceptionInInitializerError is thrown | | 2383|New|Nor|2001-06-28|BasicConfigurator's deprecated method : enableAll(| | 2498|New|Nor|2001-07-07|WriterAppender doesn't flush footer output| | 2586|New|Nor|2001-07-11|Netscpe JRE-Plugin SSL BeanInfo not found problem | | 2686|New|Enh|2001-07-19|DailyRollingFileAppender with max file size | | 2690|New|Nor|2001-07-19|DOMConfigurator cannot be compiled (org.w3c) | | 2701|New|Blk|2001-07-19|WriterAppender does not allow logging with other c| | 2726|New|Min|2001-07-21|[doc bug] incorrect explanation of priority level | | 2791|New|Enh|2001-07-25|RollingFileAppender should provide a rollover() on| | 2953|New|Maj|2001-08-01|RollingFileAppender loses log files | | 2976|New|Nor|2001-08-03|Defaultvalues in properties during configuration n| | 3008|New|Nor|2001-08-06|Log4j stopped rolling log while program was runnin| | 3023|New|Min|2001-08-07|Documentation change - JUnit version dependency | | 3058|Ass|Nor|2001-08-09|DOMConfigurator File Sharing Access log4j.dtd | | 3071|New|Min|2001-08-09|syntax error in explanatory java code | | 3105|New|Nor|2001-08-13|DailyRollingFileAppender not working correctly on | | 3607|New|Maj|2001-09-14|(log4j 1.1.3) RollingFileAppenderBeanInfo will not| | 3610|New|Nor|2001-09-14|The XPriority example is incorrect| | 3794|New|Nor|2001-09-24|TRACE priority(i.e. priority lower than DEBUG) in| | 3853|New|Min|2001-09-27|Javadoc. BasicConfigurator.configure() uses Consol| | 3915|New|Nor|2001-10-02|AsyncAppender "eats" location information | | 3933|New|Maj|2001-10-02|SocketServer Poor Performance could be improved si| | 4024|New|Nor|2001-10-08|Configuration of the Source of NTEventLogAppender | | 4090|New|Maj|2001-10-11|DailyRollingFileAppender loses logged data| | 4098|New|Enh|2001-10-11|Setting name for the FileWatchdog thread | | 4106|New|Nor|2001-10-11|DOM Configurator doesn't parse filename and line n| | 4122|New|Nor|2001-10-12|variable substitution doesn't support recursive su| | 4378|New|Min|2001-10-23|Misspelled word in FAQ| | 4561|New|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4746|New|Nor|2001-11-08|NTAppender does not use the layout speciifed in th| | 4756|New|Enh|2001-11-08|Add controls to NT Event Log appender for event #,| | 4802|New|Cri|2001-11-11|Not Serializable in Log4J 1.1.3 | | 4815|New|Nor|2001-11-12|PropertySetter ignores default properties in the j| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 4913|New|Min|2001-11-16|org.apache.log4j.helpers.FileWatchdog should allow| | 4979|New|Nor|2001-11-20|Docs issue and .ZIP missing files.| | 5211|New|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5232|New|Nor|2001-12-02|DOMConfigurator does not parse appenders if invoke| | 5393|New|Maj|2001-12-12|DailyRollingFileAppender should have rolling for n| | 5444|New|Nor|2001-12-15|AsyncAppender throws NullPointerException | | 5485|New|Nor|2001-12-18|XMLLay
Bug report for Log4j [2002/04/14]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 1459|New|Enh|2001-04-23|RollingFileAppender: keep unlimited number of back| | 1553|Ass|Enh|2001-04-27|A couple of documentation improvements| | 1669|Opn|Nor|2001-05-08|Logging 200,000 events in rapid sequence causes As| | 1960|Ass|Nor|2001-06-01|Extending the standard layout class and implementi| | 2246|New|Enh|2001-06-20|Throwable indentation & improving String escapeHTM| | 2251|New|Enh|2001-06-20|org.apache.log4j.helpers.OptionConverter's referen| | 2276|New|Nor|2001-06-21|stack trace of the exception is not getting logged| | 2377|Ass|Blk|2001-06-28|A java.lang.ExceptionInInitializerError is thrown | | 2383|New|Nor|2001-06-28|BasicConfigurator's deprecated method : enableAll(| | 2498|New|Nor|2001-07-07|WriterAppender doesn't flush footer output| | 2586|New|Nor|2001-07-11|Netscpe JRE-Plugin SSL BeanInfo not found problem | | 2686|New|Enh|2001-07-19|DailyRollingFileAppender with max file size | | 2690|New|Nor|2001-07-19|DOMConfigurator cannot be compiled (org.w3c) | | 2701|New|Blk|2001-07-19|WriterAppender does not allow logging with other c| | 2726|New|Min|2001-07-21|[doc bug] incorrect explanation of priority level | | 2791|New|Enh|2001-07-25|RollingFileAppender should provide a rollover() on| | 2953|New|Maj|2001-08-01|RollingFileAppender loses log files | | 2976|New|Nor|2001-08-03|Defaultvalues in properties during configuration n| | 3008|New|Nor|2001-08-06|Log4j stopped rolling log while program was runnin| | 3023|New|Min|2001-08-07|Documentation change - JUnit version dependency | | 3058|Ass|Nor|2001-08-09|DOMConfigurator File Sharing Access log4j.dtd | | 3071|New|Min|2001-08-09|syntax error in explanatory java code | | 3105|New|Nor|2001-08-13|DailyRollingFileAppender not working correctly on | | 3607|New|Maj|2001-09-14|(log4j 1.1.3) RollingFileAppenderBeanInfo will not| | 3610|New|Nor|2001-09-14|The XPriority example is incorrect| | 3794|New|Nor|2001-09-24|TRACE priority(i.e. priority lower than DEBUG) in| | 3853|New|Min|2001-09-27|Javadoc. BasicConfigurator.configure() uses Consol| | 3915|New|Nor|2001-10-02|AsyncAppender "eats" location information | | 3933|New|Maj|2001-10-02|SocketServer Poor Performance could be improved si| | 4024|New|Nor|2001-10-08|Configuration of the Source of NTEventLogAppender | | 4090|New|Maj|2001-10-11|DailyRollingFileAppender loses logged data| | 4098|New|Enh|2001-10-11|Setting name for the FileWatchdog thread | | 4106|New|Nor|2001-10-11|DOM Configurator doesn't parse filename and line n| | 4122|New|Nor|2001-10-12|variable substitution doesn't support recursive su| | 4378|New|Min|2001-10-23|Misspelled word in FAQ| | 4561|New|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4746|New|Nor|2001-11-08|NTAppender does not use the layout speciifed in th| | 4756|New|Enh|2001-11-08|Add controls to NT Event Log appender for event #,| | 4802|New|Cri|2001-11-11|Not Serializable in Log4J 1.1.3 | | 4815|New|Nor|2001-11-12|PropertySetter ignores default properties in the j| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 4913|New|Min|2001-11-16|org.apache.log4j.helpers.FileWatchdog should allow| | 4979|New|Nor|2001-11-20|Docs issue and .ZIP missing files.| | 5211|New|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5232|New|Nor|2001-12-02|DOMConfigurator does not parse appenders if invoke| | 5393|New|Maj|2001-12-12|DailyRollingFileAppender should have rolling for n| | 5444|New|Nor|2001-12-15|AsyncAppender throws NullPointerException | | 5485|New|Nor|2001-12-18|XMLLay
Bug report for Log4j [2002/04/21]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 1459|New|Enh|2001-04-23|RollingFileAppender: keep unlimited number of back| | 1553|Ass|Enh|2001-04-27|A couple of documentation improvements| | 1669|Opn|Nor|2001-05-08|Logging 200,000 events in rapid sequence causes As| | 1960|Ass|Nor|2001-06-01|Extending the standard layout class and implementi| | 2246|New|Enh|2001-06-20|Throwable indentation & improving String escapeHTM| | 2251|New|Enh|2001-06-20|org.apache.log4j.helpers.OptionConverter's referen| | 2276|New|Nor|2001-06-21|stack trace of the exception is not getting logged| | 2377|Ass|Blk|2001-06-28|A java.lang.ExceptionInInitializerError is thrown | | 2383|New|Nor|2001-06-28|BasicConfigurator's deprecated method : enableAll(| | 2498|New|Nor|2001-07-07|WriterAppender doesn't flush footer output| | 2586|New|Nor|2001-07-11|Netscpe JRE-Plugin SSL BeanInfo not found problem | | 2686|New|Enh|2001-07-19|DailyRollingFileAppender with max file size | | 2690|New|Nor|2001-07-19|DOMConfigurator cannot be compiled (org.w3c) | | 2701|New|Blk|2001-07-19|WriterAppender does not allow logging with other c| | 2726|New|Min|2001-07-21|[doc bug] incorrect explanation of priority level | | 2791|New|Enh|2001-07-25|RollingFileAppender should provide a rollover() on| | 2953|New|Maj|2001-08-01|RollingFileAppender loses log files | | 2976|New|Nor|2001-08-03|Defaultvalues in properties during configuration n| | 3008|New|Nor|2001-08-06|Log4j stopped rolling log while program was runnin| | 3023|New|Min|2001-08-07|Documentation change - JUnit version dependency | | 3058|Ass|Nor|2001-08-09|DOMConfigurator File Sharing Access log4j.dtd | | 3071|New|Min|2001-08-09|syntax error in explanatory java code | | 3105|New|Nor|2001-08-13|DailyRollingFileAppender not working correctly on | | 3607|New|Maj|2001-09-14|(log4j 1.1.3) RollingFileAppenderBeanInfo will not| | 3610|New|Nor|2001-09-14|The XPriority example is incorrect| | 3794|New|Nor|2001-09-24|TRACE priority(i.e. priority lower than DEBUG) in| | 3853|New|Min|2001-09-27|Javadoc. BasicConfigurator.configure() uses Consol| | 3915|New|Nor|2001-10-02|AsyncAppender "eats" location information | | 3933|New|Maj|2001-10-02|SocketServer Poor Performance could be improved si| | 4024|New|Nor|2001-10-08|Configuration of the Source of NTEventLogAppender | | 4090|New|Maj|2001-10-11|DailyRollingFileAppender loses logged data| | 4098|New|Enh|2001-10-11|Setting name for the FileWatchdog thread | | 4106|New|Nor|2001-10-11|DOM Configurator doesn't parse filename and line n| | 4122|New|Nor|2001-10-12|variable substitution doesn't support recursive su| | 4378|New|Min|2001-10-23|Misspelled word in FAQ| | 4561|New|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4746|New|Nor|2001-11-08|NTAppender does not use the layout speciifed in th| | 4756|New|Enh|2001-11-08|Add controls to NT Event Log appender for event #,| | 4802|New|Cri|2001-11-11|Not Serializable in Log4J 1.1.3 | | 4815|New|Nor|2001-11-12|PropertySetter ignores default properties in the j| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 4913|New|Min|2001-11-16|org.apache.log4j.helpers.FileWatchdog should allow| | 4979|New|Nor|2001-11-20|Docs issue and .ZIP missing files.| | 5211|New|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5232|New|Nor|2001-12-02|DOMConfigurator does not parse appenders if invoke| | 5393|New|Maj|2001-12-12|DailyRollingFileAppender should have rolling for n| | 5444|New|Nor|2001-12-15|AsyncAppender throws NullPointerException | | 5485|New|Nor|2001-12-18|XMLLay
Bug report for Log4j [2002/04/28]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 1459|New|Enh|2001-04-23|RollingFileAppender: keep unlimited number of back| | 1553|Ass|Enh|2001-04-27|A couple of documentation improvements| | 1669|Opn|Nor|2001-05-08|Logging 200,000 events in rapid sequence causes As| | 1960|Ass|Nor|2001-06-01|Extending the standard layout class and implementi| | 2246|New|Enh|2001-06-20|Throwable indentation & improving String escapeHTM| | 2251|New|Enh|2001-06-20|org.apache.log4j.helpers.OptionConverter's referen| | 2276|New|Nor|2001-06-21|stack trace of the exception is not getting logged| | 2377|Ass|Blk|2001-06-28|A java.lang.ExceptionInInitializerError is thrown | | 2383|New|Nor|2001-06-28|BasicConfigurator's deprecated method : enableAll(| | 2498|New|Nor|2001-07-07|WriterAppender doesn't flush footer output| | 2586|New|Nor|2001-07-11|Netscpe JRE-Plugin SSL BeanInfo not found problem | | 2686|New|Enh|2001-07-19|DailyRollingFileAppender with max file size | | 2690|New|Nor|2001-07-19|DOMConfigurator cannot be compiled (org.w3c) | | 2701|New|Blk|2001-07-19|WriterAppender does not allow logging with other c| | 2726|New|Min|2001-07-21|[doc bug] incorrect explanation of priority level | | 2791|New|Enh|2001-07-25|RollingFileAppender should provide a rollover() on| | 2953|New|Maj|2001-08-01|RollingFileAppender loses log files | | 2976|New|Nor|2001-08-03|Defaultvalues in properties during configuration n| | 3008|New|Nor|2001-08-06|Log4j stopped rolling log while program was runnin| | 3058|Ass|Nor|2001-08-09|DOMConfigurator File Sharing Access log4j.dtd | | 3105|New|Nor|2001-08-13|DailyRollingFileAppender not working correctly on | | 3607|New|Maj|2001-09-14|(log4j 1.1.3) RollingFileAppenderBeanInfo will not| | 3610|New|Nor|2001-09-14|The XPriority example is incorrect| | 3794|New|Nor|2001-09-24|TRACE priority(i.e. priority lower than DEBUG) in| | 3853|New|Min|2001-09-27|Javadoc. BasicConfigurator.configure() uses Consol| | 3933|New|Maj|2001-10-02|SocketServer Poor Performance could be improved si| | 4098|Ass|Enh|2001-10-11|Setting name for the FileWatchdog thread | | 4122|Opn|Nor|2001-10-12|variable substitution doesn't support recursive su| | 4561|Ass|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 5211|Ass|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5232|Ass|Nor|2001-12-02|DOMConfigurator does not parse appenders if invoke| | 5444|Ass|Nor|2001-12-15|AsyncAppender throws NullPointerException | | 5695|New|Nor|2002-01-04|Can't use log4j from two servlet contexts | | 5839|New|Maj|2002-01-14|NONE is not supported | | 5841|New|Maj|2002-01-14|Not possible with more than one category per file/| | 5846|New|Blk|2002-01-14|SocketAppender does not reconnect!! | | 5882|New|Blk|2002-01-16|Log4j does not free the appenders and resources wh| | 5932|New|Nor|2002-01-21|MDC is not working with AsyncAppender | | 5956|New|Blk|2002-01-22|JVM core dump at LocationInfo | | 6077|New|Maj|2002-01-28|readPriority() method in org.apache.log4j.spi.Logg| | 6210|New|Cri|2002-02-04|log4j in weblogic | | 6773|New|Nor|2002-02-28|LevelMatchFilter does not work in 1.2beta3| | 6860|New|Nor|2002-03-04|Filtering in Websphere 3.5.5 | | 6953|New|Nor|2002-03-07|OptionConverter Exception in Class instantiation f| | 6970|New|Nor|2002-03-07|shutdown does not close files under AsyncAppender | | 7515|Ass|Nor|2002-03-27|DailyRollingFileAppender wrong rollover type | | 7516|Opn|Enh|2002-03-27|DailyRolling
Bug report for Log4j [2002/05/05]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 1459|New|Enh|2001-04-23|RollingFileAppender: keep unlimited number of back| | 1553|Ass|Enh|2001-04-27|A couple of documentation improvements| | 1669|Opn|Nor|2001-05-08|Logging 200,000 events in rapid sequence causes As| | 1960|Ass|Nor|2001-06-01|Extending the standard layout class and implementi| | 2246|New|Enh|2001-06-20|Throwable indentation & improving String escapeHTM| | 2251|New|Enh|2001-06-20|org.apache.log4j.helpers.OptionConverter's referen| | 2276|New|Nor|2001-06-21|stack trace of the exception is not getting logged| | 2377|Ass|Blk|2001-06-28|A java.lang.ExceptionInInitializerError is thrown | | 2383|New|Nor|2001-06-28|BasicConfigurator's deprecated method : enableAll(| | 2498|New|Nor|2001-07-07|WriterAppender doesn't flush footer output| | 2586|New|Nor|2001-07-11|Netscpe JRE-Plugin SSL BeanInfo not found problem | | 2686|New|Enh|2001-07-19|DailyRollingFileAppender with max file size | | 2690|New|Nor|2001-07-19|DOMConfigurator cannot be compiled (org.w3c) | | 2701|New|Blk|2001-07-19|WriterAppender does not allow logging with other c| | 2726|New|Min|2001-07-21|[doc bug] incorrect explanation of priority level | | 2791|New|Enh|2001-07-25|RollingFileAppender should provide a rollover() on| | 2953|New|Maj|2001-08-01|RollingFileAppender loses log files | | 2976|New|Nor|2001-08-03|Defaultvalues in properties during configuration n| | 3008|New|Nor|2001-08-06|Log4j stopped rolling log while program was runnin| | 3058|Ass|Nor|2001-08-09|DOMConfigurator File Sharing Access log4j.dtd | | 3105|New|Nor|2001-08-13|DailyRollingFileAppender not working correctly on | | 3607|New|Maj|2001-09-14|(log4j 1.1.3) RollingFileAppenderBeanInfo will not| | 3610|New|Nor|2001-09-14|The XPriority example is incorrect| | 3794|New|Nor|2001-09-24|TRACE priority(i.e. priority lower than DEBUG) in| | 3853|New|Min|2001-09-27|Javadoc. BasicConfigurator.configure() uses Consol| | 3933|New|Maj|2001-10-02|SocketServer Poor Performance could be improved si| | 4098|Ass|Enh|2001-10-11|Setting name for the FileWatchdog thread | | 4122|Opn|Nor|2001-10-12|variable substitution doesn't support recursive su| | 4561|Ass|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 5211|Ass|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5232|Ass|Nor|2001-12-02|DOMConfigurator does not parse appenders if invoke| | 5444|Ass|Nor|2001-12-15|AsyncAppender throws NullPointerException | | 5695|New|Nor|2002-01-04|Can't use log4j from two servlet contexts | | 5839|New|Maj|2002-01-14|NONE is not supported | | 6210|New|Cri|2002-02-04|log4j in weblogic | | 6773|New|Nor|2002-02-28|LevelMatchFilter does not work in 1.2beta3| | 6860|New|Nor|2002-03-04|Filtering in Websphere 3.5.5 | | 6953|New|Nor|2002-03-07|OptionConverter Exception in Class instantiation f| | 6970|New|Nor|2002-03-07|shutdown does not close files under AsyncAppender | | 7515|Ass|Nor|2002-03-27|DailyRollingFileAppender wrong rollover type | | 7516|Opn|Enh|2002-03-27|DailyRollingFileAppender support for TimeZones| | 7550|Ass|Min|2002-03-28|DailyRollingFileAppender defaults to HALF_DAY rota| | 8505|Opn|Maj|2002-04-25|LOG4J - No stacktrace on unix platform| | 8527|New|Nor|2002-04-25|TelnetAppender accept()ing on closed socket after | | 8529|New|Maj|2002-04-25|JDBCAppender doesn't take throwable stack trace | | 8682|New|Nor|2002-04-30|Logger hand
Bug report for Log4j [2002/05/12]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 4561|Ass|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 5211|Ass|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5695|Ass|Nor|2002-01-04|Can't use log4j from two servlet contexts | | 8505|Opn|Maj|2002-04-25|LOG4J - No stacktrace on unix platform| | 8529|New|Maj|2002-04-25|JDBCAppender doesn't take throwable stack trace | +-+---+---+--+--+ | Total9 bugs | +---+ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9155] New: - LoggingEvent.getMDCCopy() should set mdcLookupRequired = false
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9155>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9155
LoggingEvent.getMDCCopy() should set mdcLookupRequired = false
Summary: LoggingEvent.getMDCCopy() should set mdcLookupRequired =
false
Product: Log4j
Version: 1.2
Platform: All
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
In the following method in LoggingEvent.java
public
void getMDCCopy() {
if(mdcLookupRequired) {
ndcLookupRequired = false;
// the clone call is required for asynchronous logging.
// See also bug #5932.
Hashtable t = (Hashtable) MDC.getContext();
if(t != null) {
mdcCopy = (Hashtable) t.clone();
}
}
}
ndcLookupRequired is set to false when it should be mdcLookupRequired which is
set to false.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9155] - LoggingEvent.getMDCCopy() should set mdcLookupRequired = false
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9155>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9155 LoggingEvent.getMDCCopy() should set mdcLookupRequired = false [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-17 10:27 --- Good catch! I'll fix it immediately and will release log4j 1.2.1 afterwards. By the way, did you detect this bug by reading the code or by observing at deployment time? Regards, Ceki ps: I'll also add a test case in order detect such silly errors as early as possible. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9155] - LoggingEvent.getMDCCopy() should set mdcLookupRequired = false
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9155>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9155 LoggingEvent.getMDCCopy() should set mdcLookupRequired = false --- Additional Comments From [EMAIL PROTECTED] 2002-05-17 10:36 --- I spotted this reading the code (or rather using find). I don't think that this would actualy have an issue in a deployed system. The only issues would be if you called getMDCCopy() before calling getNDC() which would then not cache the NDC localy. However you don't do that so it should be ok. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Bug report for Log4j [2002/05/19]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 4561|Ass|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 5211|Ass|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5695|Ass|Nor|2002-01-04|Can't use log4j from two servlet contexts | | 8505|Opn|Maj|2002-04-25|LOG4J - No stacktrace on unix platform| | 8529|New|Maj|2002-04-25|JDBCAppender doesn't take throwable stack trace | | 9150|New|Maj|2002-05-16|No check in FileAppender if parent-path exists| +-+---+---+--+--+ | Total 10 bugs | +---+ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9268] New: - Chainsaw does not load xml log files properly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9268>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9268 Chainsaw does not load xml log files properly Summary: Chainsaw does not load xml log files properly Product: Log4j Version: 1.2 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Other AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Chainsaw does not load the xml content from a file properly. The messages part gets truncated. Content: sendMessage():OK The contents are displayed as follows: Time: 05:14:43 Priority: FATAL Thread: RemoteEventAdapter: eigroup.sms.clients.smsbean.SMSBean@58015a NDC: null Category: com.twii.jme.server.util.integration.msp.MSPFactory Location: null Message: K Throwable: null -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9285] New: - SyslogWriter 's bug for multibyte enviroment
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9285>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9285
SyslogWriter 's bug for multibyte enviroment
Summary: SyslogWriter 's bug for multibyte enviroment
Product: Log4j
Version: unspecified
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: Normal
Priority: Other
Component: Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Hi,
I'm using log4j package(Version is 1.2.1) in project.
As Happen, when I used SyslogAppender and SyslogWriter for syslogd.
Written word is unperfectly to syslogd's "messages" file.
This word is so short than I expect that.
I thought, it's a enviroment problem with unicode.
Because I use log4j on multibyte enviroment.
(Spec:Fujitsu Solalis SunBlade 1000)
Then, I read log4j package's sources. I detected un-appropiate codes.
Next code is referd for "SyslogWriter.java".
> public
> void write(String string) throws IOException {
>DatagramPacket packet = new DatagramPacket(string.getBytes(),
>string.length(),
>address, SYSLOG_PORT);
>
>if(this.ds != null)
> ds.send(packet);
>
> }
"DatagramPacket()" 's second parameter is "string.length()".
But I thought. This suitable code is "string.getBytes().length".
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9291] New: - Default Initialization Procedure doc misleading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9291>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9291
Default Initialization Procedure doc misleading
Summary: Default Initialization Procedure doc misleading
Product: Log4j
Version: 1.2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Minor
Priority: Other
Component: Configurator
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Step 1 of the Default Initialization Procedure is misleading. Between the
name "defaultInitOverride" and the use of a negative ("any value other than
false"), I found it confusing as to what I was supposed to do. I had to look at
the code before I understood what the doc was saying. I suggest deprecating
this property name in favor of one that makes it clear what you are doing -
namely, that the default initialization process can be stopped by specifying a
particular property value.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9291] - Default Initialization Procedure doc misleading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9291>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9291 Default Initialization Procedure doc misleading [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2002-05-21 19:15 --- Good point. Altough a propeerty name such as "skipDefaultInit" is more descriptive, I am wary of changing the name for backward compatibility reasons. The documentation needs improvement that is for sure. Thanks for the bug report. -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9305] New: - Use thread context class loader for loading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305 Use thread context class loader for loading Summary: Use thread context class loader for loading Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Configurator AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The current use of Class.forName in classes like org.apache.log4j.xml.DOMConfigurator restrict flexibility of how appenders, filters, etc. may be loaded into the VM. When used in an application server this forces all dynamcially loaded objects to be in the same classpath namespace that loaded the log4j.jar. There is no drawback to using the thread context class loader instance of Class.forName and there are many advantages. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9305] - Use thread context class loader for loading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305 Use thread context class loader for loading --- Additional Comments From [EMAIL PROTECTED] 2002-05-22 07:12 --- There is one drawback to accessing the thread context class loader. It is a privaledged operation that can result in a SecurityException. The same flexibility can be achieved by allowing one to set the ClassLoader the configurator uses to load classes. Then the caller can decide to use the thread context class loader or whatever loader they choose. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9305] - Use thread context class loader for loading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305 Use thread context class loader for loading [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2002-05-22 08:29 --- Scott, I'm on this. Will reply fully in 30 minutes. -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9305] - Use thread context class loader for loading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305 Use thread context class loader for loading --- Additional Comments From [EMAIL PROTECTED] 2002-05-22 09:22 --- Scott, This what I started writing: --- BEGIN The following is from the docs/HISTORY file Release of log4j-1.2beta4 - Replaced the custom class loading based on the thread context class loader with a simple Class.forName() call. This solves two allied but distinct problems encountered when using Ant with JUnit although the bug is more general. In one instance of the problem, log4j would throw java.lang.NoClassDefFoundError for org/apache/log4j/AppenderSkeleton where log4j.jar and related classes were clearly available to the Ant classloader. In another incarnation, log4j would reject a custom appender claiming that it is not assignable to a org.apache.log4j.Appender variable. This would occur when log4j.jar was available to both the Ant classloader and the system classloader. Thanks to Dave Herman for providing detailed scenarios exposing the issues involved. See http://forum.java.sun.com/thread.jsp?forum=38&thread=70946 http://forum.java.sun.com/thread.jsp?forum=38&thread=70946#479697 http://marc.theaimsgroup.com/?l=ant-user&m=101139178705895&w=2 for more details. [*] In conclusion, while loading classes through the context class loader has advantages, it also has disadvantages. I would like to learn more about the exact scenario you are confronted with before making a decision. Moreover, please be more specific about the "many advantages" you see. --- END - Then I started reading the discussion threads on forum.java.sun.com to check whether the fix in log4j-1.2beta4 still made sense. (Until log4j-1.2beta4, alpha and beta versions of log4j used the context class loader.) Fortunately, I also had test cases reproducing the issues that Dave Herman had observed. In one scenario, log4j-1.2beta2.jar was available to the ANT class loader but not to the system class loader. Still in the same scenario, a custom appender, named foo.MyAppender, would be available to system class loader but not to the ANT class loader. In this scenario, running a simple test case that tried to configure log4j by instantiating foo.MyAppender and adding it to the root logger would fail with the following error. junit: [junit] Running foo.junit.MyTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.05 sec [junit] Output: [junit] debug: Test case <= org.apache.tools.ant.AntClassLoader [junit] debug: Thread context <= sun.misc.Launcher$AppClassLoader [junit] [junit] Testsuite: foo.junit.MyTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.05 sec [junit] - Standard Output --- [junit] debug: Test case <= org.apache.tools.ant.AntClassLoader [junit] debug: Thread context <= sun.misc.Launcher$AppClassLoader [junit] - --- [junit] [junit] Testcase: testCustomAppender took 0.04 sec [junit] Caused an ERROR [junit] org/apache/log4j/AppenderSkeleton [junit] java.lang.NoClassDefFoundError: org/apache/log4j/AppenderSkeleton [junit] at java.lang.ClassLoader.defineClass0(Native Method) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:297) [junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:253) [junit] at org.apache.log4j.helpers.Loader.loadClass(Loader.java:124) [junit] at org.apache.log4j.helpers.OptionConverter.instantiateByClassName (OptionConverter.java:313) [junit] at org.apache.log4j.helpers.OptionConverter.instantiateByKey (OptionConverter.java:116) [junit] at org.apache.log4j.PropertyConfigurator.parseAppender (PropertyConfigurator.java:619) So AppenderSkeleton could not be found because log4j-1.2beta2.jar was not available to the system class loader and as no context class loader was set, the context class loader used defaulted to the system class loader. As I said previously, changing log4j code to use only Class.forName for class loading solves the above problem since both log4j-1.2beta2.jar and foo.MyAppender are available to the ANT class loader and its parent the system class loader. In the original scenario that Dave Herman had in mind, both the syst
DO NOT REPLY [Bug 9305] - Use thread context class loader for loading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305 Use thread context class loader for loading --- Additional Comments From [EMAIL PROTECTED] 2002-05-22 09:35 --- My response is that there is no need to choose Class.forName or the TCL. Simply add a setClassLoader(ClassLoader loader) method to the configurator and then it is the framework user's choice of how the framework integrates with its usage context class loading policy. Default the configurator loader to getClass ().getClassLoader() and there is no change in behavior by default. As to examples of where Class.forName fails: 1. Bootstrap a minimal app server with a minimal configuration with the log4j.jar in the classpath 2. Load the full app server configuration from a remote web server. This includes an extended log4j configuration and any number of filters, appenders, etc. that are loaded by the URLClassLoader associated with the web server. This is a child of the class loader used during the bootstrap and so its classes are not visible to Class.forName invocations made from the log4j.jar classes. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9305] - Use thread context class loader for loading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305 Use thread context class loader for loading --- Additional Comments From [EMAIL PROTECTED] 2002-05-22 10:35 --- > My response is that there is no need to choose Class.forName or the > TCL. Simply add a setClassLoader(ClassLoader loader) method to the > configurator and then it is the framework user's choice of how the > framework integrates with its usage context class loading > policy. Default the configurator loader to getClass > ().getClassLoader() and there is no change in behavior by default. Sounds very reasonable. > As to examples of where Class.forName fails: 1. Bootstrap a minimal > app server with a minimal configuration with the log4j.jar in the > classpath 2. Load the full app server configuration from a remote web > server. This includes an extended log4j configuration and any number > of filters, appenders, etc. that are loaded by the URLClassLoader > associated with the web server. This is a child of the class loader > used during the bootstrap and so its classes are not visible to > Class.forName invocations made from the log4j.jar classes. If I undestand correctly, the bootstrap server will load a simple log4j config, create a URLClassLoader, and reconconfigure log4j with a more sophisticated configuration loaded by the URLClassLoader. Is that correct? Now, assuming the TCL was set to the URLClassLoader, if log4j configurators used the TCL to load and instantiate classes by name, this would also work for you. Yes? Thus, we have three alternatives. 1) Log4j configurators use the class loader specified by the user, as you just suggested. 2) Log4j configurators use the TCL as a first alternative and only then Class.forName. 3) Use the CL specified by the user. If none is specified, revert to 2. I am inclined to offer just 2 immediately and 3 at a later stage. Would that be good enough for you? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9305] - Use thread context class loader for loading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305 Use thread context class loader for loading --- Additional Comments From [EMAIL PROTECTED] 2002-05-22 16:00 --- Option 2 works fine as I can just as easily ensure the TCL is correct. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9349] New: - WriterAppender ignoresThrowable handling reversed
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9349>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9349
WriterAppender ignoresThrowable handling reversed
Summary: WriterAppender ignoresThrowable handling reversed
Product: Log4j
Version: 1.2
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Appender
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Found while creating a new GUI Appender based on WriterAppender.java. In the
following source code from WriterAppender.java, it looks like throwable
information will be outputted even if the Layout does not process error
information. I believe the line should be: "if(!layout.ignoresThrowable())..."
if(layout.ignoresThrowable()) {
String[] s = event.getThrowableStrRep();-
if (s != null) {
int len = s.length;
for(int i = 0; i < len; i++) {
this.qw.write(s[i]);
this.qw.write(Layout.LINE_SEP);
}
}
Haven't tested to confirm that it will be outputted because most layouts in the
base product ignore throwable information. But even if the information is not
sent, there would be a performance hit on processing something that probably
won't be outputted by the Layout.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9349] - WriterAppender ignoresThrowable handling reversed
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9349>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9349 WriterAppender ignoresThrowable handling reversed [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-05-23 14:32 --- Marc, The existent code is consistent with the indetended logic. If the layout ignores the exception, the WriterAppender will output it one line at a time. If the layout does not ignore the exception, i.e. it handles it, then there is no need for WriterAppender to output it a second time. There is no option for not output exceptions, except if the layout lies about the way it handles exceptions. I am marking this bug as RESOLVED INVALID. -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9357] New: - Misleading warning: result of incorrect code in ConsoleLogger
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9357>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9357
Misleading warning: result of incorrect code in ConsoleLogger
Summary: Misleading warning: result of incorrect code in
ConsoleLogger
Product: Log4j
Version: 1.2
Platform: All
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Appender
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I have not used log4j, I was just looking through the source code and spotted this
minor detail. So
don't take my word for it, I assume you'll double check.
Steps to reproduce:
1. Creating a
ConsoleLogger with a target of "System.err" sets the target properly.
(target="System.err";)
2. Then calling setTarget with a bogus value results in targetWarn
being called which informs the user that "System.out" will be used as a default (when
really
System.err has been set successfully in the previous operation).
Fix:
#Line 80
<<
LogLog.warn("Using System.out (default).");
>> LogLog.warn("Using " + target + " (set
previously).");
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9285] - SyslogWriter 's bug for multibyte enviroment
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9285>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9285 SyslogWriter 's bug for multibyte enviroment [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-24 11:48 --- Mr. Kadota, You are absolutely right. The computation of the byte array length is wrong. Just fixed in CVS. The fix will be available in log4j 1.2.3 when that is released. Thank you for the very professionnal bug report. -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9291] - Default Initialization Procedure doc misleading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9291>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9291 Default Initialization Procedure doc misleading [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-24 12:55 --- Log4j version 1.2.3 contains a small documentation improvement related to the description of the defaultInitOverride property. As such, I making this bug as RESOLVED FIXED. -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9268] - Chainsaw does not load xml log files properly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9268>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9268 Chainsaw does not load xml log files properly --- Additional Comments From [EMAIL PROTECTED] 2002-05-24 15:00 --- I observed this behaviour, too, when using the Xerces 2 XML parser. When using Crimson, the message is not truncated. I think, the problem is located in method XMLFileHandler.characters(...). Every time this method is invoked, a new String is created and assigned to the field storing the message. Instead it should be appended until the end of the element is reached, because parsers are allowed to deliver the characters (for the element content) in chunks, e.g. by multiple calls to the characters-method. In addition, there are message display problems, when the message contains end-of-line characters. It would be nice, if Chainsaw could handle them. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9268] - Chainsaw does not load xml log files properly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9268>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9268 Chainsaw does not load xml log files properly --- Additional Comments From [EMAIL PROTECTED] 2002-05-24 15:20 --- I am indeed using Xerces. Specifically the one that ships with Xalan 2.3.1, i.e. Xerces-J 2.0.0 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9394] New: - Test for Moderation...
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9394>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9394 Test for Moderation... Summary: Test for Moderation... Product: Log4j Version: unspecified Platform: Other URL: http://nagoya.apache.org/ OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Other AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Sorry, this should be the last test... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9394] - Test for Moderation...
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9394>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9394 Test for Moderation... [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-24 16:39 --- Fixed. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9285] - SyslogWriter 's bug for multibyte enviroment
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9285>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9285 SyslogWriter 's bug for multibyte enviroment --- Additional Comments From [EMAIL PROTECTED] 2002-05-24 15:30 --- Mr.Ceki, I appreciate your quickly response. Thank you. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9397] New: - org/apache/log4j/jmx/T.java missing package statement.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9397>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9397 org/apache/log4j/jmx/T.java missing package statement. Summary: org/apache/log4j/jmx/T.java missing package statement. Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Other AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In log4j 1.2 and 1.2.3, file org/apache/log4j/jmx/T.java has no package statement. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9268] - Chainsaw does not load xml log files properly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9268>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9268 Chainsaw does not load xml log files properly [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-25 12:40 --- As correctly identified, the code has a bug and does not handle multiple calls to characters(). I have fixed the bug and tested with Crimson and Xerces under JDK1.3.1 and JDK1.4. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Bug report for Log4j [2002/05/26]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 4561|Ass|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 5211|Ass|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5695|Ass|Nor|2002-01-04|Can't use log4j from two servlet contexts | | 8505|Ass|Maj|2002-04-25|LOG4J - No stacktrace on unix platform| | 8529|New|Maj|2002-04-25|JDBCAppender doesn't take throwable stack trace | | 9150|New|Maj|2002-05-16|No check in FileAppender if parent-path exists| | 9305|Ass|Enh|2002-05-22|Use thread context class loader for loading | | 9357|New|Nor|2002-05-23|Misleading warning: result of incorrect code in Co| | 9397|New|Nor|2002-05-24|org/apache/log4j/jmx/T.java missing package statem| +-+---+---+--+--+ | Total 13 bugs | +---+ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9435] New: - Chainsaw incorrectly loads priority (level) from XML log file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9435>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9435
Chainsaw incorrectly loads priority (level) from XML log file
Summary: Chainsaw incorrectly loads priority (level) from XML log
file
Product: Log4j
Version: 1.2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
example log entry looks like:
...
Chainsaw (from log4j 1.2.1) displays it as priority DEBUG.
I think the error is in method XMLFileHandler.startElement(...):
The line
Priority = Priority.toPriority(aAtts.getValue("level"));
is incorrect in my opinion, because the attribute name in the log4j.dtd
is "priority". As a consequence, Chainsaw is using the default log level
(DEBUG).
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9438] New: - Counter of logging-events missing
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9438>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9438
Counter of logging-events missing
Summary: Counter of logging-events missing
Product: Log4j
Version: 1.2
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
You can use the LOG4J for creating the correct return-code of your application
(you need the highest level).
For more flexibility please verify, if it's possible to implement methods like
- public int getNumberOfDebugs() {...}
- public int getNumberOfInformations() {...}
- public int getNumberOfWarnings() {...}
- public int getNumberOfErrors() {...}
- public int getNumberOfFatals() {...}
>From my point of view only a feww changes inside the class 'Logger.java' are
necessary :
...
private int debugCounter = 0;
private int infoCounter= 0;
private int warningCounter = 0;
private int errorCounter = 0;
private int fatalCounter = 0;
...
//---
//--- overwritten from Category.java
//---
public void debug(Object message)
{
debugCounter++;
super.debug(message);
}
//---
public void debug(Object message, Throwable t)
{
debugCounter++;
super.debug(message, t);
}
//---
public void info(Object message)
{
infoCounter++;
super.info(message);
}
//---
public void info(Object message, Throwable t)
{
infoCounter++;
super.info(message, t);
}
//---
public void warn(Object message)
{
warningCounter++;
super.warn(message);
}
//---
public void warn(Object message, Throwable t)
{
warningCounter++;
super.warn(message, t);
}
//---
public void error(Object message)
{
errorCounter++;
super.error(message);
}
//---
public void error(Object message, Throwable t)
{
errorCounter++;
super.error(message, t);
}
//---
public void fatal(Object message)
{
fatalCounter++;
super.fatal(message);
}
//---
public void fatal(Object message, Throwable t)
{
fatalCounter++;
super.fatal(message, t);
}
//---
//--- public
//---
public int getNumberOfDebugs()
{ return debugCounter; }
//---
public int getNumberOfInformations()
{ return infoCounter; }
//---
public int getNumberOfWarnings()
{ return warningCounter; }
//---
public int getNumberOfErrors()
{ return errorCounter; }
//---
public int getNumberOfFatals()
{ return fatalCounter; }
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9435] - Chainsaw incorrectly loads priority (level) from XML log file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9435>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9435 Chainsaw incorrectly loads priority (level) from XML log file --- Additional Comments From [EMAIL PROTECTED] 2002-05-28 07:27 --- Note, that this error only occurs, when the XML log file was created with an "old" Log4J version 1.1.x. Log4J 1.2.x creates the event attribute "level" as expected by Chainsaw. (But the distributed log4j.dtd in src/java/org/apache/log4j/xml still lists "priority" as attribute name, so I was a little confused.) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9435] - Chainsaw incorrectly loads priority (level) from XML log file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9435>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9435 Chainsaw incorrectly loads priority (level) from XML log file --- Additional Comments From [EMAIL PROTECTED] 2002-05-28 12:59 --- The problem is that the XMLLayout class is generating XML that does not conform to the DTD. It uses "level" instead of "priority" as the DTD would suggest. I was faced with the problem of chosing between making Chainsaw support: - the DTD, but not work with 1.1 code - what the XMLLayout class generates, but not work with 1.2 code - some kludge that would support both. A kludge is required as there is no log4j version information in the output generated by XMLLayout Not liking kludges I went for the second option. The question is, should we: - fix XMLLayout to support the DTD; - put a kludge in Chainsaw to support "level" and "priority" - do both of the above. I will do whatever Ceki recommends. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9435] - Chainsaw incorrectly loads priority (level) from XML log file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9435>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9435 Chainsaw incorrectly loads priority (level) from XML log file [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2002-05-28 14:02 --- The DTD should be updated to something like: Notice the two changes category -> logger and priority -> level. I'll also update XMLLayout to conform to the dtd. When chainsaw follows suite, we'll release log4j 1.2.4. There is no point in mulling over this for ages. Reading XMLLayouts is relatively new feature such that the number of upset users by the backward compatibility problem is likely to be low. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9459] New: - org.apache.log4j.varia.LevelRangeFilter is missing from 1.2.3
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9459>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9459 org.apache.log4j.varia.LevelRangeFilter is missing from 1.2.3 Summary: org.apache.log4j.varia.LevelRangeFilter is missing from 1.2.3 Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Other AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] org.apache.log4j.varia.LevelRangeFilter appears to be missing in version 1.2.3. It was in 1.2, but I don't see it in 1.2.3. Is it deprecated or is it a build problem? If it's going away, is there an alternative? I was using it like this: -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9462] New: - make default initialization available as a public method
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9462>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9462 make default initialization available as a public method Summary: make default initialization available as a public method Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Other AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] the default initialization logic, which i believe used be the Category class static initialization, looks like it is now the LogManager class static initialization. however, i believe it should be an externally callable static method instead. we have a need to reinitialize log4j on-demand, and had to copy the code out of the Category static block to do so. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9462] - make default initialization available as a public method
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9462>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9462 make default initialization available as a public method [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2002-05-28 17:16 --- Doug, Why you have to duplicate the logic of the LogManager static initializatier? Various configurators exist for the purpose of configuring log4j. Have you looked at ProperitesConfogirator or DOMConfigurator? There is no intention on making the LogManager static initializatier publicly accessible. I am marking this bug as RESOLVED WONTFIX. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9459] - org.apache.log4j.varia.LevelRangeFilter is missing from 1.2.3
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9459>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9459 org.apache.log4j.varia.LevelRangeFilter is missing from 1.2.3 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-28 17:28 --- Loren, Apparently the file LevelRangeFilter.java was not added to the 1_2 brach. I'll fix this immediately. It'll appear in log4j 1.2.4 when it comes out. In the mean time you can copy it from 1.2.0 (or CVS) and rebuild the jar file. Thanks for letting us know. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9462] - make default initialization available as a public method
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9462>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9462 make default initialization available as a public method [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX | --- Additional Comments From [EMAIL PROTECTED] 2002-05-28 17:35 --- hmmm... what's the point of default initialization if it can only be used once? if i have to explicitly pick a Configurator to re-initialize, why don't i have to explicitly pick a Configurator to initialize in the first place? if i use first-time initialization that can handle different types of Configurators, then i also want reinitialization that can. looking at it from the other side, even if you don't see the benefit in this, what's the harm in making the default initialization code publicly callable? what does it break? it should be a very minor change. thanks for your consideration. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9435] - Chainsaw incorrectly loads priority (level) from XML log file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9435>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9435 Chainsaw incorrectly loads priority (level) from XML log file [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-29 11:56 --- put in the fix as requested by Ceki. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9506] New: - Tool to debug appender duplications
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9506>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9506 Tool to debug appender duplications Summary: Tool to debug appender duplications Product: Log4j Version: unspecified Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Appender AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The FAQ describes the typical causes of duplicate logging as due to duplicate appenders. However, there is no easy way to detect where the duplicate appenders are. It would be really nice if I could flip some kind of switch (ex: set some kind of environment variable) that would cause all appenders to announce themselves, and which loggers they are attached to. This would help me track down the offending appenders when I have duplicate log entries. The announcements could be part of the log record. This is similar to the C in the PatternLayout, except C doesn't include appender info, and only works if the configuration is read. If I have appenders that somehow get a Basic configuration, they won't dump out this info. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9514] New: - Chainsaw cannot load files if messages contain CDATA
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514 Chainsaw cannot load files if messages contain CDATA Summary: Chainsaw cannot load files if messages contain CDATA Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Other AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If I try and load an XML file where messages have CDATA sections Chainsaw stops dead in its tracks. It will process the file until it comes across the first offending message. Example entry: ]]> There is no problem loading the same message using a SocketAppender. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9514] - Chainsaw cannot load files if messages contain CDATA
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514 Chainsaw cannot load files if messages contain CDATA --- Additional Comments From [EMAIL PROTECTED] 2002-05-30 11:56 --- Could you please attach a file containing some samples that do not work. The snippet below gives an error about a missing . This under both Xerces and Crimson parsers. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9514] - Chainsaw cannot load files if messages contain CDATA
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514 Chainsaw cannot load files if messages contain CDATA --- Additional Comments From [EMAIL PROTECTED] 2002-05-30 12:09 --- That's exactly the problem, it sees the nested CDATA and gets all confused. As it is clearly obvious there is a closing tag. I suspect that this eventuality is not catered for when parsing using SAX, it probably sees the end tag of the second CDATA and associates this with the first. Thus everything is now out of sync. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9514] - Chainsaw cannot load files if messages contain CDATA
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514 Chainsaw cannot load files if messages contain CDATA --- Additional Comments From [EMAIL PROTECTED] 2002-05-30 12:12 --- IANAL but can an XML CDATA section be nested like the snippet below. Just looked at http://www.w3schools.com/xml/xml_cdata.asp and it implies this is not legal. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9514] - Chainsaw cannot load files if messages contain CDATA
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514 Chainsaw cannot load files if messages contain CDATA --- Additional Comments From [EMAIL PROTECTED] 2002-05-30 12:20 --- So the question now is whose duty is it to protect against this. I would dare say that this lies with Log4J as the application should not have to care what the underlying Layout is. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9514] - Chainsaw cannot load files if messages contain CDATA
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514 Chainsaw cannot load files if messages contain CDATA --- Additional Comments From [EMAIL PROTECTED] 2002-05-30 17:11 --- Regarding "Comments From Guy Djemal 2002-05-30 12:20", I think that it is the responsibility of XMLLayout to deal with embedded CDATA sections since it is using CDATA to define the message, NCD and throwable elements. I will provide a fix shortly. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9514] - Chainsaw cannot load files if messages contain CDATA
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514 Chainsaw cannot load files if messages contain CDATA --- Additional Comments From [EMAIL PROTECTED] 2002-05-30 19:01 --- Created an attachment (id=1979) Patch: org\apache\log4j\xml\XMLLayout.java -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9514] - Chainsaw cannot load files if messages contain CDATA
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514 Chainsaw cannot load files if messages contain CDATA [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Bug report for Log4j [2002/06/02]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 569|Ver|Cri|2001-02-09|fully qualified class name used as category name c| | 851|Ass|Min|2001-03-05|DOM Configurator not throwing exception when targe| | 900|New|Cri|2001-03-08|RollingFileAppender does not work properly under W| | 4561|Ass|Nor|2001-11-01|Log4J threads don't seem to terminate incase of th| | 4861|Ass|Min|2001-11-14|log4j:ERROR Failed to flush writer| | 5211|Ass|Nor|2001-11-30|DailyRollingFileAppender should check renameTo res| | 5695|Ass|Nor|2002-01-04|Can't use log4j from two servlet contexts | | 8505|Ass|Maj|2002-04-25|LOG4J - No stacktrace on unix platform| | 8529|New|Maj|2002-04-25|JDBCAppender doesn't take throwable stack trace | | 9150|New|Maj|2002-05-16|No check in FileAppender if parent-path exists| | 9305|Ass|Enh|2002-05-22|Use thread context class loader for loading | | 9357|New|Nor|2002-05-23|Misleading warning: result of incorrect code in Co| | 9397|New|Nor|2002-05-24|org/apache/log4j/jmx/T.java missing package statem| | 9438|New|Nor|2002-05-27|Counter of logging-events missing| | 9462|Opn|Enh|2002-05-28|make default initialization available as a public | | 9506|New|Enh|2002-05-29|Tool to debug appender duplications | +-+---+---+--+--+ | Total 16 bugs | +---+ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9592] New: - Logger.getLogger(String, LoggerFactory) caching bug
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592
Logger.getLogger(String, LoggerFactory) caching bug
Summary: Logger.getLogger(String, LoggerFactory) caching bug
Product: Log4j
Version: 1.2
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The problem lies in the existing org.apache.log4j.Hierarchy line 254. The
CategoryKey used to access the Logger instance cache only uses the
String "name" param, which may only be a portion of the full category name if
a custom factory is used. So if the cache is not empty for String name, it
returns the existing logger instance and does not call
factory.makeNewLoggerInstance(name) which may produce a category with a
different name. Assuming a custom factory's makeNewLoggerInstance(String)
always returns a Logger instance with the same category name given the same
string parameter, you could cache with a CategoryKey of
customLoggerFactory.getClass().getName() + name. However if
factory.makeNewLoggerInstance("myName").getName().equals
(factory.makeNewLoggerInstance("myName").getName()) isn't true you still have
the same problem. IMHO I think the caching needs to be put in the factory
itself.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9592] - Logger.getLogger(String, LoggerFactory) caching bug
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592 Logger.getLogger(String, LoggerFactory) caching bug --- Additional Comments From [EMAIL PROTECTED] 2002-06-03 22:35 --- Created an attachment (id=1995) JUnit Test Case demonstrating bug -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9592] - Logger.getLogger(String, LoggerFactory) caching bug
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592 Logger.getLogger(String, LoggerFactory) caching bug --- Additional Comments From [EMAIL PROTECTED] 2002-06-03 22:36 --- Created an attachment (id=1996) Sample Consumer of Logger.getLogger(String,LoggerFactory) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9592] - Logger.getLogger(String, LoggerFactory) caching bug
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592 Logger.getLogger(String, LoggerFactory) caching bug --- Additional Comments From [EMAIL PROTECTED] 2002-06-03 22:37 --- Created an attachment (id=1997) Custom LoggerFactory which produces contatinated category names -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9592] - Logger.getLogger(String, LoggerFactory) caching bug
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592 Logger.getLogger(String, LoggerFactory) caching bug --- Additional Comments From [EMAIL PROTECTED] 2002-06-03 22:40 --- Can you explain what you are trying to in English for mortals please? What is the context? Thank you. -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9592] - Logger.getLogger(String, LoggerFactory) caching bug
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592 Logger.getLogger(String, LoggerFactory) caching bug --- Additional Comments From [EMAIL PROTECTED] 2002-06-03 22:46 --- Simplified description: Logger.getLogger(String,LoggerFactory) caches incorrectly. If class A calls this with 'foo' as the String param (and it's the first time the method's been called with 'foo'), the Logger instance for class A is cached. When class B makes the call with 'foo' string value, class A's logger instance is returned. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9592] - Logger.getLogger(String, LoggerFactory) caching bug
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9592 Logger.getLogger(String, LoggerFactory) caching bug [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2002-06-03 22:51 --- Yes, that is the intended behavior. The name of logger is determinant factor not the class that calls for the logger's creation. I am closing this bug. If you wish to discuss it further please do so on log4j-dev. Bugzilla is not the most appropriate means of communications to discuss enhacements. Thanks. -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9606] New: - NTEventLogAppender.dll missing in .zip file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9606>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9606 NTEventLogAppender.dll missing in .zip file Summary: NTEventLogAppender.dll missing in .zip file Product: Log4j Version: 1.2 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: Appender AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The NTEventLogAppender.dll is missing (was in \src\java\org\apache\log4j\nt in 1.1.3) in the jakarta-log4j-1.2.3.zip distribution file. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9645] New: - Add rolloverPath attribute to DailyRollingFileAppender
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9645>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9645
Add rolloverPath attribute to DailyRollingFileAppender
Summary: Add rolloverPath attribute to DailyRollingFileAppender
Product: Log4j
Version: 1.2
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Appender
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I would like to suggest a new attribute "rolloverPath" be added to the
DailyRollingFileAppender class. In short, the rolloverPath (configurable via a
property) could point to a new location to which rolled-over files could be
copied. The code samples below illustrate how we have implemented this
feature. For brevitys sake, Ive included code snippets instead of the entire
org.apache.log4j.DailyRollingFileAppender.java file that we've enhanced. The
sample code should be read in the context of Log4J 1.2.2
DailyRollingFileAppender.java source.
First, I added the following Javadoc:
* An optional rolloverPath may be specified such
* that files that are rolled over will be created in the location
* specified by this path. Any parent path information in the original
* logfile name is ignored when the rollover occurs.
* rolloverPath may be absolute or relative.
*
* If in the previous example the rolloverPath is set to
* /archive, the logging file /foo/bar.log
* will be copied to /archive/bar.log.2001-02-16 and
* logging will continue normally.
*/
Added new attributes:
/**
* Pathname and directory (File object) used if files are to archive to
* a different location than where the lof file is created.
*/
private String rolloverPath;
private File rolloverDir;
Added a new constructor:
/**
* Instantiate a DailyRollingFileAppender and open the
* file designated by filename. Files that are rolled
* over are archived to the location specified by the
* rolloverPath
*/
public DailyRollingFileAppender(Layout layout, String rolloverPath,
String filename, String datePattern)
throws IOException {
this( layout, filename, datePattern );
setRolloverPath( rolloverPath );
}
Also added the setRolloverPath() method:
/**
* Sets the location to which log files will be rolled over . If the
* given path already exists, it must be writable and must be a
* directory. If it doesn't exist, it will get created, along with any
* necessary, non-existent parent directories.
*/
public void setRolloverPath( String pathName ) {
rolloverPath = pathName;
rolloverDir = new File( rolloverPath );
// Check to see if the rollover path exists (needs to be created)
// and if we can write to it.
if ( rolloverDir.exists() ) {
if ( !rolloverDir.isDirectory() ) {
LogLog.warn( "The path name " + pathName + " does not refer to a
directory." );
rolloverDir = null;
}
else if ( !rolloverDir.canWrite() ){
LogLog.warn( "Unable to write to directory " +
rolloverDir.getAbsolutePath() );
rolloverDir = null;
}
}
else if ( !rolloverDir.mkdirs() ) {
LogLog.warn( "Unable to create rollover directory for " +
rolloverPath );
rolloverDir = null;
}
}
Updated the rollover() method:
.
.
.
/* If rolloverDir was specified, ignore any path information in
* the original filename and use the rolloverPath instead. */
// File target = new File(scheduledFilename); // Original code
File target;
if ( rolloverDir == null ) {
target = new File( scheduledFilename );
}
else {
target = new File( rolloverDir,
(new File(scheduledFilename)).getName() );
}
.
.
.
//LogLog.debug(fileName +" -> "+ scheduledFilename); // Original code
LogLog.debug(fileName +" -> "+ target.getPath());
.
.
.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9606] - NTEventLogAppender.dll missing in .zip file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9606>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9606 NTEventLogAppender.dll missing in .zip file --- Additional Comments From [EMAIL PROTECTED] 2002-06-06 11:36 --- It is also missing in the .tar.gz file. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9462] - make default initialization available as a public method
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9462>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9462 make default initialization available as a public method [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-06-06 20:52 --- I am closing this bug report. If you wish to continue this discussion please supply a patch to log4j-dev@ for the changes you'd like to see. Thanks, -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9514] - Chainsaw cannot load files if messages contain CDATA
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514 Chainsaw cannot load files if messages contain CDATA --- Additional Comments From [EMAIL PROTECTED] 2002-06-06 20:59 --- Michael, Thank you for supplying the patch. -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9738] New: - Should Hierarchy.resetConfiguration also reset LogLog?
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9738>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9738 Should Hierarchy.resetConfiguration also reset LogLog? Summary: Should Hierarchy.resetConfiguration also reset LogLog? Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: Minor Priority: Other Component: Configurator AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] We are using the PropertiesConfigurator.configureAndWatch to setup log4j and monitor changes to our log4j.properties file. I occasionally need to turn on the LogLog messages (to debug appenders). With our setup, I just add log4j.debug= to the log4j.properties file and the change is applied after the "watch" cycle detects the file change. Unfortunately, when I remove the log4j.debug= property declaration, the LogLog messages are not turned off (perhaps because the resetConfiguration method in the LoggerRepository implementation doesn't clear the flag checked by LogLog?). Is there a workaround? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9606] - NTEventLogAppender.dll missing in .zip file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9606>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9606 NTEventLogAppender.dll missing in .zip file [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 16:58 --- This will be corrected when log4j 1.2.4 is released (shortly). Thank you for the bug report. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9645] - Add rolloverPath attribute to DailyRollingFileAppender
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9645>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9645 Add rolloverPath attribute to DailyRollingFileAppender [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||REMIND --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:12 --- Good suggestion. However, DailyRollingFileAppender is now considered legacy code. Log4j 1.3 will have a different mechanism for rolling files. We will make sure to take your suggestion into account before 1.3 is released. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9738] - Should Hierarchy.resetConfiguration also reset LogLog?
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9738>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9738 Should Hierarchy.resetConfiguration also reset LogLog? [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:14 --- Have you tried the following? log4j.debug=false -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9438] - Counter of logging-events missing
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9438>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9438 Counter of logging-events missing [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:19 --- One solution is to write an appender which collects/exposes this information. It won't be added to Logger class. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9506] - Tool to debug appender duplications
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9506>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9506 Tool to debug appender duplications [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:21 --- Have you tried log4j.debug=true this annouces when appenders are attached to loggers. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9305] - Use thread context class loader for loading
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9305 Use thread context class loader for loading [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:31 --- No news, good news. Closing the report. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9357] - Misleading warning: result of incorrect code in ConsoleLogger
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9357>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9357 Misleading warning: result of incorrect code in ConsoleLogger [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:36 --- Thanks. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9750] New: - Using AsynchAppender in logging configuration prevents virtual machine from exiting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750 Using AsynchAppender in logging configuration prevents virtual machine from exiting Summary: Using AsynchAppender in logging configuration prevents virtual machine from exiting Product: Log4j Version: 1.2 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Minor Priority: Other Component: Appender AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I am using log4j to provide logging for a tomcat web application. I am initializing log4j as described in http://jakarta.apache.org/log4j/docs/manual.html : I am placing log4j.jar in WEB-INF/lib I am placing log4jconfig.xml in WEB-INF/classes and I am specifing the system property log4j.configuration=log4jconfig.xml when starting the servlet container. Normally I can start tomcat, perform a few simple operations that create log entries, and shutdown tomcat properly (remote connection triggers process end). However, when I use a configuration that includes an AsynchAppender, different behaviour occurs. Tomcat starts as normal, the program progress and log entries happen as normal, but when tomcat is shut down, the virtual machine does not end. I have been able to reproduce this problem with a very simple test case, which I will attach shortly. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9750] - Using AsynchAppender in logging configuration prevents virtual machine from exiting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750 Using AsynchAppender in logging configuration prevents virtual machine from exiting --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:39 --- Created an attachment (id=2049) java source code that reproduces the issue -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9750] - Using AsynchAppender in logging configuration prevents virtual machine from exiting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750 Using AsynchAppender in logging configuration prevents virtual machine from exiting --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:39 --- Created an attachment (id=2050) log4j config that causes the console to hang -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9750] - Using AsynchAppender in logging configuration prevents virtual machine from exiting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750 Using AsynchAppender in logging configuration prevents virtual machine from exiting --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:40 --- Created an attachment (id=2051) log4j config that causes the console not to hand -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9750] - Using AsynchAppender in logging configuration prevents virtual machine from exiting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750 Using AsynchAppender in logging configuration prevents virtual machine from exiting --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:41 --- Created an attachment (id=2052) log4j jar file used in test case (log4j.jar from v 1.2.3) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9750] - Using AsynchAppender in logging configuration prevents virtual machine from exiting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750 Using AsynchAppender in logging configuration prevents virtual machine from exiting --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:41 --- Created an attachment (id=2053) log4j.dtd used in test runs (from v 1.2.3) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9397] - org/apache/log4j/jmx/T.java missing package statement.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9397>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9397 org/apache/log4j/jmx/T.java missing package statement. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||LATER --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:42 --- This is "normal" in the sense that the T class is just a toy class. JMX support in log4j needs more work. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9750] - Using AsynchAppender in logging configuration prevents virtual machine from exiting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750 Using AsynchAppender in logging configuration prevents virtual machine from exiting --- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:45 --- This test case was compiled and run using JDK1.4 It should run in earlier versions with the addition of an xml parser. compiled with "javac -classpath log4j.jar Test.java" the nohang case is run with "%JAVA_HOME_14%\bin\java -cp log4j.jar;. - Dlog4j.configuration=log4jconfig_nohang.xml Test" it generated the following output: 2002-06-10 11:36:59,874: DEBUG (test) - starting 2002-06-10 11:36:59,889: DEBUG (test) - finishing the hanging case is run with "C:\log4j_case>%JAVA_HOME_14%\bin\java -cp log4j.jar;. -Dlog4j.configuration=log4jconfig_hang.xml Test" it generates the same output: 2002-06-10 11:37:04,670: DEBUG (test) - starting 2002-06-10 11:37:04,670: DEBUG (test) - finishing except that execution does not stop. The process continues until forcibly terminated (Ctrl-C on the console, for example). If you need any other test cases, or if I have missed any information you would like to have, please let me know. Sean Reilly -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9750] - Using AsynchAppender in logging configuration prevents virtual machine from exiting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9750
Using AsynchAppender in logging configuration prevents virtual machine from exiting
--- Additional Comments From [EMAIL PROTECTED] 2002-06-10 17:53 ---
Potential solution:
I believe that the VM is continuing execution because the thread created by
AsyncAppender is not a daemon thread. If this thread were to be set as a
Daemon thread then the VM should be able to exit properly.
Here is a change to the constructor of Dispatcher (internal class in
AsyncAppender) that would accomplish this:
Before:
Dispatcher(BoundedFIFO bf, AsyncAppender container) {
this.bf = bf;
this.container = container;
this.aai = container.aai;
// set the dispatcher priority to lowest possible value
this.setPriority(Thread.MIN_PRIORITY);
this.setName("Dispatcher-"+getName());
// set the dispatcher priority to MIN_PRIORITY plus or minus 2
// depending on the direction of MIN to MAX_PRIORITY.
//+ (Thread.MAX_PRIORITY > Thread.MIN_PRIORITY ? 1 : -1)*2);
}
After:
Dispatcher(BoundedFIFO bf, AsyncAppender container) {
this.bf = bf;
this.container = container;
this.aai = container.aai;
this.setDaemon(true);
// set the dispatcher priority to lowest possible value
this.setPriority(Thread.MIN_PRIORITY);
this.setName("Dispatcher-"+getName());
// set the dispatcher priority to MIN_PRIORITY plus or minus 2
// depending on the direction of MIN to MAX_PRIORITY.
//+ (Thread.MAX_PRIORITY > Thread.MIN_PRIORITY ? 1 : -1)*2);
}
This of course leaves the appender vunerable to the possibility of a VM
shutdown resulting in logging message loss. If this is an issue, then perhaps
a finalizer could be added that would call the dispatcher's close() method?
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9843] New: - reload configurations loaded by the Default Initialization Procedure
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9843>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9843 reload configurations loaded by the Default Initialization Procedure Summary: reload configurations loaded by the Default Initialization Procedure Product: Log4j Version: 1.1 Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Configurator AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The deault initialization http://jakarta.apache.org/log4j/docs/manual.html#defaultInit is perfomed in a static block of Category.java. This should be moved into a public method and then called from the static block when Category is loaded. Then the public method could be called later to re-run the default initialization and reload any changes. There should also be a system property to watch the configuration file loaded by the default initialization procedure and reload it when changes are made. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9843] - reload configurations loaded by the Default Initialization Procedure
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9843>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9843 reload configurations loaded by the Default Initialization Procedure [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-06-13 17:41 --- *** This bug has been marked as a duplicate of 9462 *** -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9462] - make default initialization available as a public method
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9462>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9462 make default initialization available as a public method [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-06-13 17:41 --- *** Bug 9843 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9879] New: - Hierarchy constructor is not backward compatible
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9879>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9879
Hierarchy constructor is not backward compatible
Summary: Hierarchy constructor is not backward compatible
Product: Log4j
Version: 1.2
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
We use a third-party library ("realMethods") that uses Log4j, and also use
Log4j in our own code. I recently tried to upgrade to Log4j 1.2.1, which is
supposed to be a drop-in replacement for 1.1.3, but it isn't.
The constructor for Hierarchy changed from Hierarchy(Category) to Hierarchy
(Logger). This means the existing code that tries to pass a Category to the
constructor can't be compiled.
RealMethods could change their library to work with Log4j 1.2 by switching from
Category to Logger, but then it wouldn't work for people who are still using
Log4j 1.1. I believe Hierarchy should be able to accept a Category in its
constructor; or, failing that, documentation of 1.2's backward compatbility
(such as http://jakarta.apache.org/log4j/docs/download.html) should mention the
issue.
Thanks.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 9738] - Should Hierarchy.resetConfiguration also reset LogLog?
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9738>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9738 Should Hierarchy.resetConfiguration also reset LogLog? [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Additional Comments From [EMAIL PROTECTED] 2002-06-14 20:35 --- Guess I should've tried that before posting... Thx. :-) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 10140] New: - chainsaw can not view xml in a log message
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10140>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10140 chainsaw can not view xml in a log message Summary: chainsaw can not view xml in a log message Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Severity: Minor Priority: Other Component: Other AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] If you log xml with a [CDATA[12345]] piece in it chainsaw stops loading at the event with the CDATA. It would stop with the event below. Also chainsaw does not display the xml message, it only shows the last tag.
DO NOT REPLY [Bug 10140] - chainsaw can not view xml in a log message
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10140>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10140 chainsaw can not view xml in a log message --- Additional Comments From [EMAIL PROTECTED] 2002-06-21 22:29 --- which version of log4j are you using? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 10140] - chainsaw can not view xml in a log message
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10140>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10140 chainsaw can not view xml in a log message --- Additional Comments From [EMAIL PROTECTED] 2002-06-22 15:36 --- Is the example complete? I don't see the closing tags nor . Second, CDATA sections are coded as "". Is the "[CDATA[12344.000]]" representation correct? If your XML file actually contains "<[CDATA[12344.000]]>", then this may be a repeat of bug http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9514 which is fixed in Log4J 1.2.4. Finally, the second tag doesn't seem right if you are logging a valid XML document that is being sent or received by your application. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
DO NOT REPLY [Bug 10185] New: - AsyncAppender.close() does not call close() on attached appenders
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10185>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10185 AsyncAppender.close() does not call close() on attached appenders Summary: AsyncAppender.close() does not call close() on attached appenders Product: Log4j Version: 1.2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Appender AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I sent a message to the log4j-dev mailing list, which Ceki replied to. Here is his reply: "You are correct to observe that AsyncAppender.close does not close embedded appenders. The rationale behind this behavior is that embedded appenders might be attached somewhere else, so closing them when AsyncAppender is closed would be somewhat heavy handed and possibly incorrect. This "foresightful" reasoning is doubtful because attaching the same appender to more than one logger is often problematic and consequently discouraged. It would much simpler if AsyncAppender.close also closed embedded appenders. I would appreciate if you could enter a bug report so that the problem is not forgotten. (I admit its a problem.)" -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
