Re: Is it me or FilterBasedTriggeringPolicy has a bug!

I believe that the behavior is designed to mimic the logic of the filter's in AppenderSkeleton.  If no filter
either chooses to accept or deny the request it is assumed to be accepted.  If the desired behavior is to deny
any request that is not explicitly accepted or denied, then the last filter in the chain should be a DenyAllFilter.

FilterBasedTriggeringPolicy is final since the intended method of changing its behavior is by changing
the filters in the policy.  Marking a class final should be the default since it is not possible to add final
after a class is published without breaking compatibility, however it is always allowable to remove
final and preserve compatibility.  See Effective Java's discussions on designing for extension or
prohibiting it.

Bug report for Log4j [2011/04/03]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
|     |   |           MIN=Minor   NOR=Normal    ENH=Enhancement TRV=Trivial |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting  |
|17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads  |
|20395|Inf|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|23329|New|Enh|2003-09-22|<logger> element in XML config should support reso|
|26084|Inf|Nor|2004-01-13|Log Event detail panel does not show special chara|
|27363|Inf|Enh|2004-03-02|JNI based SyslogAppender                          |
|27367|Inf|Enh|2004-03-02|NetSendAppender                                   |
|29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM|
|29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe|
|30055|New|Nor|2004-07-12|Problem with registering Appenders with the same n|
|30407|Inf|Maj|2004-07-30|Externally rolled file problem                    |
|30888|Inf|Maj|2004-08-27|Chainsaw mixes files in same panel                |
|30892|New|Min|2004-08-27|Log files cannot be closed                        |
|31089|New|Nor|2004-09-07|Does not accept ISO8601 dates in focus field      |
|31178|Inf|Cri|2004-09-11|Exception using Chainsaw for simple debugging     |
|31179|Ass|Enh|2004-09-11|Implement Chainsaw as Eclipse stand-alone applicat|
|33278|New|Min|2005-01-27|NPE thrown durring daily log file rollover        |

DO NOT REPLY [Bug 50213] Category callAppenders synchronization causes java.lang.Thread.State: BLOCKED - synchronization can be avoided by using immutable AppenderAttachableImpl

https://issues.apache.org/bugzilla/show_bug.cgi?id=50213

--- Comment #6 from bartosz <kowalewski.bartosz <at> gmail.com> 2011-04-04 06:28:51 EDT ---
Hi guys,

When doing performance/load tests of my system, I've been observing plenty of
threads waiting on this synchronization - on
org.apache.log4j.Category.callAppenders(). For sure a deadlock is not possible
and, what is more, this suboptimal synchronization mechanism cannot cause HUGE
performance degradation if async appenders are used underneath. However, in a
really multithreaded env it'll cause some delays.

It should not be hard to improve this synchronization mechanism without the
need to change API. Introduce a read-write lock? 

Log4j 1.2.x is compliant with JDK 1.2, right? If so, using
java.util.concurrent.locks classes is not an option. Maybe a simple custom impl
of read-write lock would be enough?

Best regards,
  Bartek

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Avoiding the unnecessary message build cost

DO NOT REPLY [Bug 51025] New: PropertyConfigurator does not properly set up ErrorHandler

https://issues.apache.org/bugzilla/show_bug.cgi?id=51025

           Summary: PropertyConfigurator does not properly set up
                    ErrorHandler
           Product: Log4j
           Version: 1.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Configurator
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: g <at> raphaelli.com

Created an attachment (id=26858)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=26858)
Patch to ErrorHandlerTestCase to expose issue with 1.2.16 PropertyConfigurator

When configuring log4j using a properties-style file an appender's error
handler is not set up properly.  Attached to this bug are two patches:

 - fix the ErrorHandlerTestCase to expose this bug - the current test is
picking up the results from the first test run resulting in a false positive
suceess.

 - update PropertyConfigurator to set the appender on the defined ErrorHandler,
as xml.DOMConfigurator does, plus a set of fixes to parse the property file
correctly.  fixing parsing without the appender fix results in a npe, as there
is no primary appender.  fixing the the appender without the parser updates
prevents a failback appender from ever being configured.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

DO NOT REPLY [Bug 51025] PropertyConfigurator does not properly set up ErrorHandler

https://issues.apache.org/bugzilla/show_bug.cgi?id=51025

--- Comment #1 from graph <g <at> raphaelli.com> 2011-04-05 17:20:02 EDT ---
Created an attachment (id=26859)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=26859)
Update PropertyConfigurator to process errorhandler directives

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Re: Avoiding the unnecessary message build cost

See the LogMF or LogSF classes.  LogMF used MessageFormat type format specifiers ("{1}") while LogSF uses
SLF4J format specifiers ("{}") .

varargs were introduced in Java 5 and have an unavoidable array construction/destruction expense even if
the level is not reached.  The LogMF and LogSF classes approximate the usability of varargs by having a lot
of different signatures.

On Apr 4, 2011, at 10:27 AM, <g.x.cusano.pineda <at> accenture.com> <g.x.cusano.pineda <at> accenture.com> wrote:

> Hi,
>       why don't we add a method in the Logger class or at least a Util with a method like the following one in order to
avoid the cost of the message build.
>       In this way we'll not have to build the message unless the priority is enabled for the logger.
>  
>       I'll wait for your thoughts.
>  
> Regards,
>  
> import org.apache.log4j.Logger;
> import org.apache.log4j.Priority;
>  
> public class LoggerUtil {
>  
>     static public void log(Logger logger, Priority priority, Object... objs){
>  
>         if (logger.isEnabledFor(priority) ){
>             StringBuffer sb = new StringBuffer();
>             for(Object obj : objs){
>                 sb.append( obj.toString() );
>             }
>             logger.log(priority, sb.toString() );
>         }
>     }
> }
>  
>  
> Cusano Pineda, Gerardo H.
> Information System Engineer
> Accenture – System Integration & Technology
> Buenos Aires, Argentina
> * g.x.cusano.pineda <at> accenture.com
> 
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise
private information. If you have received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.

DO NOT REPLY [Bug 51027] New: Stuck Thread due to lock contention with RollingFileAppender

https://issues.apache.org/bugzilla/show_bug.cgi?id=51027

           Summary: Stuck Thread due to lock contention with
                    RollingFileAppender
           Product: Log4j
           Version: 1.2
          Platform: HP
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: Appender
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: jazz_003 <at> hotmail.com

Currently my client is using Weblogic Platform along with log4j to do the
logging for their added on system module.

So far we have been randomly hitted with Stuck threads in weblogic and Oracle
support has highlighted that the issue to this is due to the deadlock with
RollingFileAppender.

Is there a fix to this?

Thanks

"[STUCK] ExecuteThread: '68' for queue: 'weblogic.kernel.Default
(self-tuning)'" daemon prio=7 tid=004b0cc0 nid=911 lwp_id=4390440 waiting for
monitor entry [46a40000..46a40bd0]
at org.apache.log4j.Category.callAppenders(Category.java:185)
- waiting to lock <75980e20> (a org.apache.log4j.Logger)
at org.apache.log4j.Category.forcedLog(Category.java:372)
at org.apache.log4j.Category.info(Category.java:674)
at com.starhub.bss.common.ta.TALogger.log(TALogger.java:110)
at
com.starhub.bss.spl.web.common.ProcessDefinitionBase.log(ProcessDefinitionBase.java:91)
at
com.starhub.bss.spl.web.instructionmanager.control.CtrlDBFormOrderImpl.printOrderDAO(CtrlDBFormOrderImpl.java:565)
at
com.starhub.bss.spl.web.instructionmanager.control.CtrlDBFormOrderImpl.getOrderXML(CtrlDBFormOrderImpl.java:303)
at
com.starhub.bss.spl.web.instructionmanager.control.CtrlDBFormOrderBean.getOrderXML(CtrlDBFormOrderBean.java:204)
at sun.reflect.GeneratedMethodAccessor1032.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.bea.wli.knex.runtime.jcs.container.JcsProxy.invokeBeehiveControl(JcsProxy.java:666)
at com.bea.wli.knex.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:433)
at $Proxy202.getOrderXML(Unknown Source)
at
com.starhub.bss.eai.integration.web.billingprovision.BillingProvision.ctrlDBFormOrderGetOrderXML(BillingProvision.java:407)
at sun.reflect.GeneratedMethodAccessor1031.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.wli.bpm.runtime.Perform.invoke(Perform.java:39)
at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:50)
at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:93)
at com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:217)
at com.bea.wli.bpm.runtime.ProcessState.dispatchRequest(ProcessState.java:241)
at
com.bea.wli.bpm.runtime.JpdContainer.dispatchProcessRequest(JpdContainer.java:1077)
at com.bea.wli.bpm.runtime.JpdContainer.preInvoke(JpdContainer.java:1041)
at com.bea.wli.knex.runtime.core.container.Invocable.invoke(Invocable.java:248)
at com.bea.wli.bpm.runtime.JpdContainer.invoke(JpdContainer.java:814)
at

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

DO NOT REPLY [Bug 51027] Stuck Thread due to lock contention with RollingFileAppender

https://issues.apache.org/bugzilla/show_bug.cgi?id=51027

Curt Arnold <carnold <at> apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Curt Arnold <carnold <at> apache.org> 2011-04-07 01:02:47 EDT ---
Support questions should go on log4j-users <at> apache.org.  There may be a bug in
there, but there is not enough to determine what it is or where it lies.  Your
thread dump was truncated.  The thread stack that was shown is expected when
another thread is in the process of logging.  What is needed is to see the
stack trace on the other thread which apparently holds a lock on logger.  If
there is a call inversion, there could be a deadlock.

In addition, it is always good to report the version of log4j in use and
whether the behavior occurs with the current release version and extra points
if the current SVN head is tested.  Operating system and JVM can also be
helpful.

Marking as invalid, please post again on log4j-user with more info.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Bug report for Log4j [2011/04/10]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
|     |   |           MIN=Minor   NOR=Normal    ENH=Enhancement TRV=Trivial |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting  |
|17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads  |
|20395|Inf|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|23329|New|Enh|2003-09-22|<logger> element in XML config should support reso|
|26084|Inf|Nor|2004-01-13|Log Event detail panel does not show special chara|
|27363|Inf|Enh|2004-03-02|JNI based SyslogAppender                          |
|27367|Inf|Enh|2004-03-02|NetSendAppender                                   |
|29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM|
|29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe|
|30055|New|Nor|2004-07-12|Problem with registering Appenders with the same n|
|30407|Inf|Maj|2004-07-30|Externally rolled file problem                    |
|30888|Inf|Maj|2004-08-27|Chainsaw mixes files in same panel                |
|30892|New|Min|2004-08-27|Log files cannot be closed                        |
|31089|New|Nor|2004-09-07|Does not accept ISO8601 dates in focus field      |
|31178|Inf|Cri|2004-09-11|Exception using Chainsaw for simple debugging     |
|31179|Ass|Enh|2004-09-11|Implement Chainsaw as Eclipse stand-alone applicat|
|33278|New|Min|2005-01-27|NPE thrown durring daily log file rollover        |
|33493|Inf|Enh|2005-02-10|contribution to log4j: servlet diagnostic context |
|34440|New|Nor|2005-04-13|sandbox:IMAppender - comma-seperated recipient lis|
|34491|Ver|Nor|2005-04-18|Missing include in build.jms target results in mis|
|34651|New|Enh|2005-04-27|allow for a header on top of every rolled file    |
|34738|Inf|Nor|2005-05-04|Chainsaw does not remember what Columns are select|
|34945|Inf|Nor|2005-05-17|ThrowableInformation has dubious Stack Trace extra|
|34974|Inf|Cri|2005-05-19|Exception when running a Pluglet                  |
|35239|Inf|Nor|2005-06-06|NullPointerException when saving displayed events |
|35563|Inf|Enh|2005-06-30|Syslog appender parametrability                   |
|35996|Inf|Enh|2005-08-03|Add support for ant-like <property> in log4j.xml  |
|36435|New|Enh|2005-08-31|Log4J RollingFileAppender under OpenVMS does not f|
|36654|Inf|Min|2005-09-14|Provide better error messages for "Please initiali|
|36789|Inf|Nor|2005-09-23|Empty control flow statement in org.apache.log4j.l|
|37638|New|Nor|2005-11-25|logging doesn't fall back with FallbackErrorHandle|
|37734|New|Nor|2005-12-01|Customize Event ID and Event Category with NTEVent|
|38363|Ass|Nor|2006-01-24|SecurityException during log output               |
|38394|Ver|Enh|2006-01-26|PropertySetter fails to print stacktrace if error |
|38395|Ver|Reg|2006-01-26|Unable to set threshold on appender via config fil|
|38406|Ver|Nor|2006-01-26|jdk1.4 dependencies in log4j 1.3 alpha            |
|38513|New|Nor|2006-02-05|[PATCH] Suggested unit test for JMSAppender       |
|38582|Ass|Nor|2006-02-08|Chainsaw does not include Receiver JavaDoc in dist|
|38590|Inf|Nor|2006-02-09|no space on device fails another instance         |
|38883|Opn|Nor|2006-03-07|LogFilePatternReceiver fails to process multi-line|
|39690|Inf|Cri|2006-05-31|Initialization fail in J2EE Environment           |
|39691|Ass|Nor|2006-05-31|DBAppender doesn't log long events                |
|40068|New|Nor|2006-07-18|Add support for attach-on-demand API to chainsaw  |
|40251|Opn|Min|2006-08-14|Hard coded JMX domain name for MBean instances    |
|40382|Inf|Maj|2006-09-01|Sysappender hangs during boot time on HP          |
|40385|Inf|Maj|2006-09-01|SocketServer cannot find config file when passed a|
|40472|New|Nor|2006-09-11|SettingsManager calls loadSettings with global set|
|40533|New|Nor|2006-09-18|Chainsaw not showing all logging statements       |
|40570|Inf|Blk|2006-09-21|RollingFileAppender does not rollover when the fil|
|40611|New|Trv|2006-09-27|Bad subclass example; NullPointerException in Logg|
|40736|Inf|Nor|2006-10-11|log4j delete permission denied                    |
|40889|Inf|Nor|2006-11-03|repeated entries in log after failure             |
|40990|Inf|Nor|2006-11-17|Cannot bind port or ip address for outgoing UDP so|
|41006|Inf|Enh|2006-11-20|Contributing XMLSocketHubReceiver                 |
|41214|Ass|Maj|2006-12-19|Deadlock with RollingFileAppender                 |
|41311|Inf|Min|2007-01-06|Please make TimeBasedRollingPolicy non-final?     |
|41547|Inf|Nor|2007-02-05|PropertyConfigurator and layout.contentType       |
|41799|New|Enh|2007-03-09|SyslogAppender should enable to customize Log4j.Le|
|41882|Inf|Nor|2007-03-18|IE7 problems with Log4J web site                  |
|41980|Inf|Maj|2007-03-29|Log4j stop updating log file- version log4j-1.2.8 |
|42189|Ass|Nor|2007-04-22|Add simple bridge for java.util.logging, with basi|
|42213|Opn|Blk|2007-04-24|log4j causing threads to stuck in weblogic        |
|42516|Inf|Nor|2007-05-24|Log4j failed to log file when packaged in Eclipse |
|42664|New|Enh|2007-06-14|JUL Appender                                      |
|42883|Opn|Nor|2007-07-12|'Welcome' and 'Drag & Drop' panels can't be hidden|
|42933|Inf|Maj|2007-07-18|IllegalStateException thrown from FileAppender.clo|
|43282|Opn|Nor|2007-08-31|Add OSGi packaging info to log4j and companions   |
|43313|Ass|Nor|2007-09-05|log4j 1.2.16 release considerations and discussion|
|43619|New|Enh|2007-10-13|Simple proposal for pluggable sys-props resolvers |
|43637|Inf|Nor|2007-10-16|SocketAppender.append(LoggingEvent) calls the Erro|
|43728|Inf|Cri|2007-10-29|Log file loss when specified file is locked by ano|
|43736|Ass|Nor|2007-10-30|Chainsaw does not honor encoding when loading XML |
|43820|New|Enh|2007-11-08|[PATCH] Layered Configurator Patch                |
|43879|Inf|Nor|2007-11-16|FileAppender writes Header multiple times         |
|43911|Inf|Nor|2007-11-20|logfiles not getting rolled over with RollingFileA|
|43923|Inf|Min|2007-11-21|JBOSS specific information in javadocs            |
|44219|Inf|Nor|2008-01-13|'WARNING' for a log level is silently ignored/chan|
|44308|New|Enh|2008-01-28|[Patch] JMX component for managing Logger configur|
|44370|Inf|Reg|2008-02-06|MANIFEST.MF broken in log4j-1.2.15.jar            |
|44386|Opn|Nor|2008-02-10|NTEventLogAppender.dll for windows 64             |
|44526|Inf|Nor|2008-03-04|segmentation fault occuring when PropertyConfigura|
|44557|Inf|Nor|2008-03-07|no close call to Appender after replacing the root|
|44649|Inf|Nor|2008-03-20|JMS Hangs when a Root Appender                    |
|44700|New|Nor|2008-03-28|Log4J locks rolled log files                      |
|44727|Inf|Nor|2008-04-01|Add missing Logger#isErrorEnabled and isWarningEna|
|44834|Inf|Nor|2008-04-17|SimpleSocketServer looses buffered logs, produces |
|44839|Inf|Nor|2008-04-17|SyslogAppender logging to a UNIX domain socket    |
|44932|New|Cri|2008-05-05|improve DailyRollingFileAppender handling of rotat|
|44934|Inf|Enh|2008-05-05|add helper method to DailyRollingFileAppender to g|
|45042|New|Nor|2008-05-19|Need a reliable way to detect misconfiguration    |
|45109|Inf|Nor|2008-05-31|SMTPAppender uses wrong property for mail server  |
|45165|Ass|Enh|2008-06-09|Multifile Appender                                |
|45231|Ass|Nor|2008-06-18|Clear appenders call on logger calls a helper whic|
|45236|Inf|Cri|2008-06-19|Wriring output to an out-dated file.              |
|45304|Inf|Nor|2008-06-29|using log4j with OAS for some reasone all the logg|
|45482|Inf|Min|2008-07-25|Source contains unused variables                  |
|45629|New|Nor|2008-08-13|TopicConnection is not closed                     |
|45753|New|Nor|2008-09-06|Code contribution: BurstFilter for extras         |
|45781|New|Nor|2008-09-11|RollingFileAppender under Windows does not rotate |
|45855|New|Enh|2008-09-21|Add site/apt documentation for JULBridgeLogManager|
|45932|New|Nor|2008-10-01|Log4j JMX MBeans not cleaned up                   |
|45934|New|Enh|2008-10-02|FileAppender should use virtual-machine shutdown h|
|45939|New|Nor|2008-10-02|Cannot drop HierarchyDynamicMBean from LoggerRepos|
|46100|New|Enh|2008-10-27|NagiosAppender available for contribution         |
|46260|Inf|Nor|2008-11-21|RollingFileAppender and Tomcat has a strange behav|
|46426|Ass|Nor|2008-12-20|Implement commons-logging interfaces natively in l|
|46514|New|Nor|2009-01-12|provide API to re-init log4j                      |
|46533|New|Enh|2009-01-14|Deamon Thread                                     |
|46570|New|Nor|2009-01-20|DailyRollingFileAppender rolls logs into files dat|
|46573|Inf|Maj|2009-01-21|MDC attributes cant't be displayed on Chainsaw    |
|46592|Opn|Trv|2009-01-23|trim() on property file entries                   |
|46626|New|Enh|2009-01-29|Log4J 1.2.15 SyslogAppender doesn't not handle TAG|
|46691|New|Nor|2009-02-10|log4j file rolling over on restart of the server  |
|46804|New|Enh|2009-03-05|create the method PropertyConfigurator.configureAn|
|46868|New|Nor|2009-03-17|SocketHUBAppender: Allow restriction of binding to|
|46878|New|Cri|2009-03-19|Deadlock in 1.2.15 caused by AsyncAppender and Thr|
|46941|New|Enh|2009-03-31|Sub Level Logging Technique                       |
|46983|New|Enh|2009-04-07|More Debug output for log4j auto-configure request|
|47123|New|Blk|2009-04-29|TimeBasedRollingPolicy appends logs into a old log|
|47141|Inf|Enh|2009-05-02|add getCyclicBuffer() method to log4j SMTPAppender|
|47164|New|Enh|2009-05-07|HTMLLayout replace newline with <BR>              |
|47208|New|Enh|2009-05-17|Better Default colours for Log Panel Color Filter |
|47357|New|Min|2009-06-11|Declaring logger and category with same name cause|
|47575|Inf|Nor|2009-07-24|GZipping large files stops logging                |
|47595|Opn|Nor|2009-07-28|[companion] POMs of companions have problems      |
|47703|New|Nor|2009-08-18|Object rendering ought to be done outside synchron|
|47713|Inf|Nor|2009-08-20|SMTPAppender system properties propagation issue  |
|47740|Inf|Nor|2009-08-26|log4j 1.2.15 deadlock RootAppender NDC            |
|47883|New|Nor|2009-09-21|Lines dropped with UseNewHashFunction             |
|47898|Inf|Maj|2009-09-24|DailyRollingFileAppender unable to create backup l|
|47960|New|Min|2009-10-08|CompositeAppender contribution                    |
|48027|Inf|Cri|2009-10-20|Logger statements in a particular class file is no|
|48141|Inf|Cri|2009-11-05|Log file rotation issue in Linux VM               |
|48209|New|Nor|2009-11-17|Websphere 6.0: logging statements appear in the SY|
|48220|New|Min|2009-11-18|LoggingEvent.mdcCopy serialization with non-serial|
|48244|New|Min|2009-11-19|Socket Server configuration does not handle not re|
|48365|New|Maj|2009-12-10|Log4J DailyRollingFileAppender sometimes does not |
|48430|New|Nor|2009-12-22|log4j:ERROR Write failure. java.io.IOException: St|
|48502|New|Cri|2010-01-07|Issue: Rotation file is not getting created - Roll|
|48527|New|Maj|2010-01-11|maven metadata is out of date                     |
|48583|New|Enh|2010-01-20|allow format of timestamp (first column of log fil|
|48607|New|Cri|2010-01-25|Log levels are not displayed corectly             |
|48679|New|Nor|2010-02-04|performance of getEffectiveLevel can be significan|
|48704|New|Nor|2010-02-08|Multiple Java Process in Cluster Logging to the sa|
|48802|New|Nor|2010-02-23|Log4j not writting.                               |
|48820|New|Nor|2010-02-26|JDBCAppender inserts the current MDC values for th|
|48986|New|Nor|2010-03-25|RollingFileAppender.rollOver() calls this.setFile |
|49003|New|Nor|2010-03-27|SocketServerTestCase.test8 fails on Apache Harmony|
|49071|New|Nor|2010-04-08|1.2.16 isn't available for download               |
|49077|New|Nor|2010-04-09|Prepare smaller jar omitting LF5 and Chainsaw 1   |
|49177|New|Enh|2010-04-23|SyslogAppender: Make the maximum package size conf|
|49243|New|Min|2010-05-04|Fix one BZ number in Changelog of 1.2.16          |
|49247|New|Enh|2010-05-04|Add option for persistent/non-persistent delivery |
|49248|New|Min|2010-05-04|javadoc for org.apache.log4j.rolling.FixedWindowRo|
|49265|New|Nor|2010-05-07|log4j - java.io.OptionalDataException             |
|49307|New|Nor|2010-05-18|unusable error message when log4j.xml has a duplic|
|49349|New|Nor|2010-05-27|LoggingEvent stoped coming with AsyncAppender     |
|49353|New|Nor|2010-05-28|[patch] change logfactor userdir name to hidden di|
|49354|New|Nor|2010-05-28|XMLLayout writes illegal characters to XML file   |
|49359|New|Nor|2010-05-29|Log4j site should have some mention of git mirrori|
|49390|New|Nor|2010-06-05|1.0 releases of log4j companions component and rec|
|49421|New|Maj|2010-06-10|Chainsaw don't show Logger for SocketReceiver and |
|49470|New|Nor|2010-06-19|log4j 1.2.17 release                              |
|49481|New|Maj|2010-06-21|Log4j stops writting to file, and then causes serv|
|49489|New|Enh|2010-06-22|Ability to filter on several loggers              |
|49563|New|Min|2010-07-06|New SMTPProtocol and SMTPPort not recognized      |
|49571|New|Enh|2010-07-08|refreshing log4j - reconfigurable from log4j.prope|
|49592|New|Cri|2010-07-14|477 All Attributes Not Set                        |
|49597|New|Min|2010-07-15|The log4j.dtd is to restrictive                   |
|49693|New|Cri|2010-08-03|Intermittently Log4j fails to bind with log file  |
|49797|New|Enh|2010-08-22|AsyncAppenders Enchancement                       |
|49852|New|Enh|2010-08-31|Allow log files to rollover at any specified time |
|49853|New|Enh|2010-08-31|Adding loggers to the configuration               |
|49854|New|Nor|2010-08-31|Documentation                                     |
|49899|New|Nor|2010-09-08|PatternLayout and EnhancedPatternLayout issues wit|
|49920|New|Maj|2010-09-13|DailyRollingFileAppender.rollOver() might leave su|
|49932|New|Nor|2010-09-14|Additional OSGI/BND configuration elements        |
|50085|New|Maj|2010-10-13|SyslogAppender does not split stack traces correct|
|50164|New|Nor|2010-10-27|getAppender method in Logger class doesn't return |
|50166|New|Nor|2010-10-27|DailyRollingFileAppender and FileAppender fail to |
|50188|New|Nor|2010-10-31|Update site content to Apache Branding Requirement|
|50213|New|Nor|2010-11-04|Category callAppenders synchronization causes java|
|50225|New|Nor|2010-11-06|Filesystem placeholder not working with PropertyCo|
|50226|New|Nor|2010-11-06|Problem with placeholders and PropertyConfigurator|
|50238|New|Cri|2010-11-09|wrong log levels logged with the serialized Loggin|
|50323|New|Nor|2010-11-23|Vulnerability in NTEventLogAppender               |
|50366|New|Enh|2010-11-29|JDBCAppender Enhancement                          |
|50369|New|Min|2010-11-29|missing comma in class header javadoc for Level   |
|50433|New|Maj|2010-12-08|Drag and Drop does not work anymore               |
|50445|New|Nor|2010-12-09|Color bar is higher than scrollabr                |
|50463|New|Nor|2010-12-13|AsyncAppender causing deadlock when dispatcher thr|
|50479|New|Nor|2010-12-15|[PATCH] JMSQueueAppender - Change message object t|
|50486|New|Maj|2010-12-16|Memoryleak - org.apache.log4j.helpers.ThreadLocalM|
|50614|New|Maj|2011-01-19|Lock in CallAppenders causing all Thread to wait f|
|50641|New|Cri|2011-01-24|"Too Many Open Files" while using RollingFileAppen|
|50776|New|Enh|2011-02-14|Support TCP in SyslogAppender                     |
|50800|New|Cri|2011-02-16|log4j 1.2.16 has duplicate import-package entries |
|50817|New|Nor|2011-02-22|The JDBCAppender can't insert log info like this:h|
|50830|New|Min|2011-02-25|NPE in ISO8601DateFormat.hashCode and toString    |
|50844|New|Nor|2011-02-28|DateFormat.getDateTimeInstance() is very expensive|
|50845|New|Enh|2011-03-01|Content Assist (Ctrl + Space) needed in log4j.prop|
|50856|New|Enh|2011-03-02|Allow ignoreTCL option to be set in log4jconfig.xm|
|50858|New|Nor|2011-03-02|Classloader leak when using Log4j in a webapp cont|
|50930|New|Nor|2011-03-14|org.apache.log4jPriority methods toString(), toInt|
|50931|New|Nor|2011-03-14|unclosed http                                     |
|51025|New|Nor|2011-04-05|PropertyConfigurator does not properly set up Erro|
+-----+---+---+----------+--------------------------------------------------+
| Total  206 bugs                                                           |
+---------------------------------------------------------------------------+