logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "offbynull (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-197) log4j2 creates 2 threads per each log attempt if the remote flume agent goes down
Date Sat, 06 Apr 2013 03:29:16 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

offbynull updated LOG4J2-197:

        Fix Version/s:     (was: 2.0-beta5)
    Affects Version/s: 2.0-beta5
> log4j2 creates 2 threads per each log attempt if the remote flume agent goes down
> ---------------------------------------------------------------------------------
>                 Key: LOG4J2-197
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-197
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Flume Appender
>    Affects Versions: 2.0-beta5
>            Reporter: offbynull
>         Attachments: Screenshot.png, zzzzzzzzzzzzzzzzzTest.tar.gz
> Steps to reproduce (use attached Maven project):
> 1. Start your remote flume agent
> 2. Run the Maven project and attach to it with the debugger in your favourite IDE (I
use NetBeans)
> 3. Kill your remote flume agent
> 4. Rapidly press enter
> Each time you press Enter, 2 new threads show up. See the attached screenshot. Notice
the panel on the left is littered with new threads. I was pressing Enter rapidly for 30 seconds.
> NOTE: This also happens if the remote flume agent hasn't been started at all.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message