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

Remko Popma updated LOG4J2-315:
-------------------------------

    Attachment: log4j2.xml
                ResultStats.java

Still struggling with this. Not sure if the problem happens during the 
roll-over or during the shutdown. Could it be that making the Async thread a 
daemon thread changed the behaviour of thread.join() in the 
AsyncAppender.stop() method? Unlikely, but I thought I'd mention it...

In my workspace I have added counters and logging code to AsyncAppender without 
being able to pin down what is happening. I must have made too many changes: 
now I can't reproduce the problem any more... :-)

Sigh... I'm taking a break from this and I'll take another stab at this 
tomorrow.

If anyone is interested, I'm attaching a helper class, ResultStats, and an 
updated config file. If you use this config file to run the test program the 
log files will not be zipped so it is easier to parse them. ResultStats parses 
the resulting log files and reports the number of log events and a breakdown of 
the missing events.
(There could be many missing events so you may want to redirect the output to a 
file.)
                
> Multiple threads logging to same AsyncAppender- Data Loss
> ---------------------------------------------------------
>
>                 Key: LOG4J2-315
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-315
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>            Reporter: Sudharma Puranik
>            Assignee: Remko Popma
>            Priority: Blocker
>         Attachments: log4j2.xml, ResultStats.java, TestMultiThread.zip
>
>
> creating multiple threads which logs messages. I could see that for 5 million 
> logging messages only 4.7 million messages  are logged. Dont know what is the 
> reason but this could be something serious for auditing.

--
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-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Reply via email to