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/22 01:56:25 UTC
[jira] [Comment Edited] (LOG4J2-1324) Async Appender - Consumer
thread dying - new thread unable to start
[ https://issues.apache.org/jira/browse/LOG4J2-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205484#comment-15205484 ]
Ron Gonzalez edited comment on LOG4J2-1324 at 3/22/16 12:56 AM:
----------------------------------------------------------------
it looks like the batcheventprocessor is defaulting to the com.lmax.disruptorFatalExceptionHandler, we don't have an exception handler defined otherwise. I wonder whether the new AsyncLoggerConfig-2 thread is failing to start due to the default of "blocking strategy" lock, rather than wait strategy.
was (Author: rong):
it looks like the batcheventprocessor is defaulting to the com.lmax.disruptorFatalExceptionHandler, we don't have an exception handler. I wonder whether the new AsyncLoggerConfig-2 thread is failing to start due to the default of "blocking strategy" lock, rather than wait strategy.
> 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
> Affects Versions: 2.2
> Environment: LOG4J CORE Release Version 2.2
> Disruptor Bundle-Version 3.3.2
> Reporter: Ron Gonzalez
> Attachments: 2016-03-18_17-44-06.jpg, BatchEventProcessor.png, log4j2_config.xml
>
>
> 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