[
https://issues.apache.org/jira/browse/LOG4J2-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427578#comment-15427578
]
Leon Finker edited comment on LOG4J2-1518 at 8/19/16 4:08 AM:
--------------------------------------------------------------
Yes on Solaris. But I thought that issue was already fixed. It didn't deadlock
just once. It deadlocked on that specific service on multiple instances (3) of
that service. First two instances then were restarted fine, but 3rd instance
was restarted twice and same deadlock. The only solution was to disable async
logging and then it started. Same code is used in 100s of other services and
instances with async logging and no issues observed. The other services are
mixture of Solaris and Linux.
was (Author: leonfin):
Yes on Solaris. But I thought that issue was already fixed.
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
