[infinispan-issues] [JBoss JIRA] (ISPN-4498) OutOfMemoryError when CI is ran with tracing
RH Bugzilla Integration (JIRA)
issues at jboss.org
Tue Sep 9 07:27:02 EDT 2014
[ https://issues.jboss.org/browse/ISPN-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000263#comment-13000263 ]
RH Bugzilla Integration commented on ISPN-4498:
-----------------------------------------------
Vojtech Juranek <vjuranek at redhat.com> changed the Status of [bug 1139642|https://bugzilla.redhat.com/show_bug.cgi?id=1139642] from NEW to MODIFIED
> OutOfMemoryError when CI is ran with tracing
> --------------------------------------------
>
> Key: ISPN-4498
> URL: https://issues.jboss.org/browse/ISPN-4498
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 7.0.0.Alpha4
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 7.0.0.Alpha5
>
>
> The CI will fail very often when tracing is enabled with some sort of OOM error.
> http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_MasterHotspotJdk7trac
> Looking closer this appears to be an issue with an accumulation of Threads. These threads aren't running either but rather are held in memory unneedingly. It appears that they are being retained in the log4j1.2 NDC class in it's hashtable. Upon further investigation we never call to NDC.remove which would clear up the current any dead threads.
> I have created JBLOGGING-106 to fix this as well. In the mean time we shouldn't use NDC.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the infinispan-issues
mailing list