logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1518) Deadlock when using pure async and toString logs another message
Date Sat, 20 Aug 2016 00:25:20 GMT

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

Remko Popma commented on LOG4J2-1518:

Yes, that is the ticket I meant. Can you try if the problems still occurs when you use disruptor
3.3.5? Log4j2 should work with that version.

> Deadlock when using pure async and toString logs another message
> ----------------------------------------------------------------
>                 Key: LOG4J2-1518
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1518
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.6.2
>         Environment: Solaris
>            Reporter: Leon Finker
>            Assignee: Remko Popma
>         Attachments: 10511.jstack, async_deadlock.txt
> Hi,
> It looks like this was reported before in: LOG4J2-471
> We've encountered similar issue with one of the libraries where it's toString was indirectly
also logging. This caused a deadlock when RingBuffer was full. Please see attached stack snippet.
> According to the following docs, it's possible to set sync policy to synchronously log
the event if buffer is full. I don't see it documented. What's the policy option?
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/LOG4J2-1080
> https://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/async/AsyncQueueFullPolicyFactory.html
> Thank you

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