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] [Comment Edited] (LOG4J2-1324) Async Logger - Consumer thread dying - new thread unable to start
Date Tue, 22 Mar 2016 13:34:25 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206272#comment-15206272
] 

Ron Gonzalez edited comment on LOG4J2-1324 at 3/22/16 1:34 PM:
---------------------------------------------------------------

attaching image : !2016-03-22_8-32-37.jpg! , shows:

On Left: 
Shows default consumer thread stack trace from 
https://github.com/LMAX-Exchange/disruptor/issues/138

On Right shows:
New thread attempting to be instantiated by daemon thread factory.

We are theorizing that this means that the old thread is not exiting cleanly, releasing lock
on the object, preventing the new consumer from starting cleanly (i.e. not able to enter and
obtain the locked object).


was (Author: rong):
attaching image : 2016-03-22_8-32-37.jpg, shows:

On Left: 
Shows default consumer thread stack trace from 
https://github.com/LMAX-Exchange/disruptor/issues/138

On Right shows:
New thread attempting to be instantiated by daemon thread factory.

We are theorizing that this means that the old thread is not exiting cleanly, releasing lock
on the object, preventing the new consumer from starting cleanly (i.e. not able to enter and
obtain the locked object).

> Async Logger - 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
> ORACLE jdk1.8.0_45
>  Linux 2.6.32-573.el6.x86_64, amd64
>            Reporter: Ron Gonzalez
>         Attachments: 2016-03-18_17-44-06.jpg, 2016-03-22_8-32-37.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


Mime
View raw message