[jboss-jira] [JBoss JIRA] (WFCORE-707) System.out usage may cause deadlock

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071145#comment-13071145 ] 

James Perkins commented on WFCORE-707:
--------------------------------------

As you can see in the thread dump the deadlock is happening because a {{ConsoleAppender}} is being used. Ideally you'd just not use a log4j {{ConsoleAppender}}. Short for that [downloading|https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/logmanager/log4j-jboss-logmanager/1.1.2.Final/log4j-jboss-logmanager-1.1.2.Final.jar] the latest log4j-jboss-logmanager should fix this issue. You'd need to add the library in {{modules/system/layers/base/org/jboss/log4j/logmanager/main/}} and modify the {{modules/system/layers/base/org/jboss/log4j/logmanager/mainmodule.xml/}} file to reflect the new resource name. 

> System.out usage may cause deadlock
> -----------------------------------
>
>                 Key: WFCORE-707
>                 URL: https://issues.jboss.org/browse/WFCORE-707
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging
>            Reporter: Bart Van Dosselaer
>            Assignee: James Perkins
>         Attachments: threaddump.txt
>
>
> We recently experienced a deadlock due to the logging subsystem, exactly as was detailed in this thread: https://developer.jboss.org/thread/241453
> Our concern is that since we include a fairly large number of third-party components, we can't guarantee they're not using System.out or System.err somewhere, potentially causing a thread deadlock.
> Are there plans to review this issue, or is the only way to guarantee not having such issues, to disable the logging subsystem?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)