You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ron Gonzalez (JIRA)" <ji...@apache.org> on 2016/03/21 17:45:25 UTC

[jira] [Created] (LOG4J2-1324) Async Appender - Consumer thread dying - new thread unable to start

Ron Gonzalez created LOG4J2-1324:
------------------------------------

             Summary: 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
(v6.3.4#6332)

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