[jboss-jira] [JBoss JIRA] (WFCORE-707) System.out usage may cause deadlock
James Perkins (JIRA)
issues at jboss.org
Fri May 22 12:59:19 EDT 2015
[ https://issues.jboss.org/browse/WFCORE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070519#comment-13070519 ]
James Perkins commented on WFCORE-707:
--------------------------------------
Simply using {{System.out}} or {{System.err}} won't trigger a deadlock. The issue here was specific to the log4j {{ConsoleAppender}} and has been fixed in WildFly 9.x. If you're seeing a deadlock with something other than the {{ConsoleAppender}} please let me know. A thread dump would help too.
> 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
>
> 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)
More information about the jboss-jira
mailing list