[infinispan-issues] [JBoss JIRA] (ISPN-6475) Remove the async log4j2 appender in the test configurations
Dan Berindei (JIRA)
issues at jboss.org
Fri Apr 8 08:07:00 EDT 2016
[ https://issues.jboss.org/browse/ISPN-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189033#comment-13189033 ]
Dan Berindei commented on ISPN-6475:
------------------------------------
For now we've only noticed the OOMEs in the build with TRACE logging enabled, because there is another factor involved: {{UnitTestTestNGListener}} registers a {{UncaughtExceptionHandler}} that logs the stacks of all the threads when it handles an OOME.
The ISPN-6364 fix removes this thread dump on OOME, so it should also fix this issue. But it's the async appender doesn't improve things that much, so we should still remove it for extra safety.
> Remove the async log4j2 appender in the test configurations
> -----------------------------------------------------------
>
> Key: ISPN-6475
> URL: https://issues.jboss.org/browse/ISPN-6475
> Project: Infinispan
> Issue Type: Task
> Components: Build process, Test Suite - Server
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: testsuite_stability
> Fix For: 9.0.0.Alpha1
>
>
> {{ClientEventsOOMTest}} started generating {{OutOfMemoryError}} s again, and they are hanging the build because of LOG4J2-1361.
> We should remove the async appender, at least until LOG4J2-1361 is fixed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the infinispan-issues
mailing list