[jboss-jira] [JBoss JIRA] (JBLOGGING-117) EAP 6.4 has threadlock appears related to logging
David Lloyd (JIRA)
issues at jboss.org
Thu Jun 11 09:16:02 EDT 2015
[ https://issues.jboss.org/browse/JBLOGGING-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Lloyd resolved JBLOGGING-117.
-----------------------------------
Resolution: Rejected
This is not necessarily even a bug in this particular project. What you need to do is contact Red Hat support services and open a support case, and our support engineers will help walk you through this; otherwise, if you do not have a support agreement, the right thing to do is to visit the WildFly user forums and ask there.
Thanks.
> EAP 6.4 has threadlock appears related to logging
> -------------------------------------------------
>
> Key: JBLOGGING-117
> URL: https://issues.jboss.org/browse/JBLOGGING-117
> Project: JBoss Logging
> Issue Type: Bug
> Environment: development environment- linux
> Reporter: Bill Rodriguez
> Assignee: James Perkins
> Priority: Critical
> Attachments: threaddump4-0.log
>
>
> After our WAR starts up -- we have a 5 minute web services running and some JUI portal calls to the WAR which uses System.out.println and slf4j logger. About 5-15 after start, the app no longer processes and the web serv seems to time out trying to obtain threads-
> We capture a thread dump(attached) and it appears the bug is same bug as we saw in eap6.3-- we moved to 6.4 due to a post that said the bug had been fixed in 6.4 here:
> http://stackoverflow.com/questions/30099371/jboss-eap-6-3-threads-get-deadlock-with-log4j-consoleappender
> the above bug reference ConsoleAppender and our threaddump shows this class here:
> "http-/10.19.80.121:9080-6":
> waiting to lock monitor 0x00007ff93406cbf8 (object 0x00000000c92a9230, a org.apache.log4j.ConsoleAppender),
> It appears this bug is still present in 6.4-- and we are DEAD at the moment...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list