You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2022/05/06 10:16:00 UTC

[jira] [Commented] (LOG4J2-3500) Deadlock in Log4j

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

Gary D. Gregory commented on LOG4J2-3500:
-----------------------------------------

Hello [~G1G4] 

2.12.1 is a pretty old version. Would you be able to test on the current version 2.17.2?

> 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)