You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Aleksandr Pavlovskiy (JIRA)" <ji...@apache.org> on 2019/06/03 12:02:00 UTC

[jira] [Commented] (LOG4J2-2239) Deadlock in log4j 2.10.0

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

Aleksandr Pavlovskiy commented on LOG4J2-2239:
----------------------------------------------

Got absolutely the same issue and found that solution: [https://programmer.help/blogs/a-runnable-state-thread-hang-s-on-the-java.io.fileoutputstream.writebytes-method.html]

In short: if you click into windows console window while mouse selection option is enabled - all logging threads will hang waiting console resource.

> 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
>             Fix For: 2.10.0
>
>         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)