[
https://issues.apache.org/jira/browse/LOG4J2-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352052#comment-16352052
]
Ramon Li commented on LOG4J2-2239:
----------------------------------
Thanks Ralph, so it is a big performance issue, many threads waiting for this
thread?
> Deadlock in log4j 2.10.0
> ------------------------
>
> Key: LOG4J2-2239
> URL: https://issues.apache.org/jira/browse/LOG4J2-2239
> Project: Log4j 2
> Issue Type: Bug
> Components: API
> Affects Versions: 2.10.0
> Environment: OpenJDK 64-Bit Server VM (25.121-b13 mixed mode) in
> docker
> Reporter: Ramon Li
> Priority: Major
> Attachments: deadlock_stack.txt
>
>
> I got a problem on our server, seems the log4j dead locked, I just attached
> the thread stack in this email.
> 550 threads blocked in this line:
> java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.logging.log4j.core.appender.OutputStreamManager.writeBytes(OutputStreamManager.java:360)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
