logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Gonzalez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-1324) Async Appender - Consumer thread dying - new thread unable to start
Date Mon, 21 Mar 2016 16:45:25 GMT

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

Ron Gonzalez updated LOG4J2-1324:
    Attachment: 2016-03-18_17-44-06.jpg

> Async Appender - Consumer thread dying - new thread unable to start
> -------------------------------------------------------------------
>                 Key: LOG4J2-1324
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1324
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>            Reporter: Ron Gonzalez
>         Attachments: 2016-03-18_17-44-06.jpg
> We are seeing a situation where the consumer thread
> "AsyncLoggerConfig-1" is apparently dying.
> We do see a new consumer thread trying to start up, but it is blocked
> waiting for a lock, so no logging is happening.
> Is this a defect in log4j?
> Is the original consumer thread dying due to perhaps an unhandled exception ?
> Is that original consumer thread not terminating gracefully and
> releasing the locked object so the new consumer thread can start?
> Please see attached screenshot.  Top of screen is normal
> asyncloggerconfig thread (consumer).
> Bottom is thread trace when logging stops, we no longer see an
> "asyncloggerconfig-1" thread, instead a new thread is trying to start
> but never does "asyncloggerconfig-2".

This message was sent by Atlassian 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