[jira] [Comment Edited] (LOG4J2-3500) Deadlock in Log4j

["Gianfranco Amatore (Jira)" <ji...@apache.org>]

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

Gianfranco Amatore edited comment on LOG4J2-3500 at 5/30/22 9:32 AM:
---------------------------------------------------------------------

Hi,

Are there any other reports of this type for this version?


was (Author: JIRAUSER289039):
Hi,

Are there any other reports of this type?

> Deadlock in Log4j
> -----------------
>
>                 Key: LOG4J2-3500
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3500
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.12.1
>            Reporter: Gianfranco Amatore
>            Priority: Major
>         Attachments: tdump.2022-03-31 13_10_15.out
>
>
> I encountered a problem on our ESB (Red Hat Fuse 7.6), it seems that the log4j dead locked while writing the log file. The whole jvm remains blocked for about 10 mins, then it starts again executing. Attached the thread-dump that shows the deadlock.
>  
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)