You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2008/11/25 11:59:44 UTC
[jira] Created: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
OOM in .TestSetupAndCleanupFailure
----------------------------------
Key: HADOOP-4721
URL: https://issues.apache.org/jira/browse/HADOOP-4721
Project: Hadoop Core
Issue Type: Bug
Components: test
Affects Versions: 0.20.0
Environment: 64 bit linux with JRockit 64-bit JVM
Reporter: Steve Loughran
Assignee: Steve Loughran
Priority: Minor
The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-4721.
------------------------------------
Resolution: Won't Fix
I now think this is a problem with Ant setting up junit to log the output; at debug level this test just creates too much data. There's no solution to this within og4j or hadoop. Closing as WONTFIX.
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: log4j.properties
>
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-4721:
-----------------------------------
Attachment: log4j.properties
This is the log4J config file; its the hadoop log4j with the debug logger altered to not print the thread info -that was causing a deadlock on JRockit
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: log4j.properties
>
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Ceki Gulcu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650646#action_12650646 ]
Ceki Gulcu commented on HADOOP-4721:
------------------------------------
Looking at the source code of MiniDFSCluster.java [1], I can't see any references to logging.
What happens when you disable logging altogether? Maybe there is no memory because there is a leak somewhere unrelated to log4j.
[1] http://tinyurl.com/69soss
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: log4j.properties
>
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Ceki Gulcu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650618#action_12650618 ]
Ceki Gulcu commented on HADOOP-4721:
------------------------------------
Which one is the "debug logger"?
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: log4j.properties
>
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Ceki Gulcu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650594#action_12650594 ]
Ceki Gulcu commented on HADOOP-4721:
------------------------------------
Try setting the 'immediateFlush' property of your FileAppender to true.
If that is already the case, is it possible that the data being logged is very large?
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650629#action_12650629 ]
Steve Loughran commented on HADOOP-4721:
----------------------------------------
that's a point. Hang on, I'm not sure thats' the log4 properties file used in test runs
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: log4j.properties
>
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650952#action_12650952 ]
Steve Loughran commented on HADOOP-4721:
----------------------------------------
Ceki, we're running 1.1.15.
If I set logging to ERROR then the test succeeds in <3 minutes and all is well. Things go wrong at DEBUG level. It could be there's too much stuff coming to stdout for ant, or there could be some looping going on. Or it could be a JRockit x64 problem. I'll try some more experiments (same code under a sun JVM, more selective log levels, etc)
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: log4j.properties
>
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650524#action_12650524 ]
Steve Loughran commented on HADOOP-4721:
----------------------------------------
Stack trace
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (HADOOP-4721) OOM in
.TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on HADOOP-4721 started by Steve Loughran.
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650757#action_12650757 ]
Steve Loughran commented on HADOOP-4721:
----------------------------------------
I dont think there is a memory leak, I just fear that too much is being buffered -even on console output- though it could be hidden by Ant playing games underneath. If Ant is still buffering everything going to stdout and log4j is pushing to stdout, Ant could be the cause even though it is not in the stack trace.
I will downgrade logging level to INFO and see if that is enough to make the problem go away.
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: log4j.properties
>
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650589#action_12650589 ]
Steve Loughran commented on HADOOP-4721:
----------------------------------------
This is in this line:
LOG.info("Shutting down the Mini HDFS Cluster");
Could be something to discuss with Team Log4J. But the underlying cause is, presumably, that a few hundred MB of text are somehow being written out and neither Ant nor Log4J are happy with this.
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650586#action_12650586 ]
Steve Loughran commented on HADOOP-4721:
----------------------------------------
Patching Ant to handle this gracefully (by catching the OOM exception and skipping the conversion) shows the underlying cause, its Log4J that is running out of memory
java.lang.OutOfMemoryError: requested array is larger than heap
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at java.io.PrintStream.write(PrintStream.java:430)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
at org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:58)
at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:316)
at org.apache.log4j.WriterAppender.append(WriterAppender.java:160)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
at org.apache.log4j.Category.callAppenders(Category.java:206)
at org.apache.log4j.Category.forcedLog(Category.java:391)
at org.apache.log4j.Category.log(Category.java:856)
at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:133)
at org.apache.hadoop.hdfs.MiniDFSCluster.shutdown(MiniDFSCluster.java:550)
at org.apache.hadoop.mapred.TestSetupAndCleanupFailure.testWithDFS(TestSetupAndCleanupFailure.java:107)
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650632#action_12650632 ]
Steve Loughran commented on HADOOP-4721:
----------------------------------------
the properties file used in my test runs is
# log4j configuration used during build and unit tests
log4j.rootLogger=info,stdout
log4j.threshhold=ALL
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c{2} %x- %m%n
It's different from the one in SVN because of HADOOP-3654
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: log4j.properties
>
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650963#action_12650963 ]
Steve Loughran commented on HADOOP-4721:
----------------------------------------
The trigger for this is my having the following line in src/test/log4.properties
log4j.logger.org.apache.hadoop.mapred=DEBUG
Does anyone else see the same problem if they add this to their log4 properties file?
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: log4j.properties
>
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Ceki Gulcu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650641#action_12650641 ]
Ceki Gulcu commented on HADOOP-4721:
------------------------------------
There is nothing wrong with the above config file. Moreover, it is already configured for immediate flush which is the default.
1) Which version of log4j is this?
2) Are you really sure that the message being logged is not huge or somehow becomes huge?
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: log4j.properties
>
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650525#action_12650525 ]
Steve Loughran commented on HADOOP-4721:
----------------------------------------
Stack Trace (resent)
[junit] Exception in thread "Main Thread" java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 164626424, Num elements: 164626404
[junit] at java.util.Arrays.copyOf(Arrays.java:2786)
[junit] at java.io.ByteArrayOutputStream.toByteArray(ByteArrayOutputStream.java:133)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:448)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768)
[junit] Running org.apache.hadoop.mapred.TestSetupAndCleanupFailure
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit] Test org.apache.hadoop.mapred.TestSetupAndCleanupFailure FAILED (timeout)
This is in ant,
if (startTestSuiteSuccess) {
sendOutAndErr(new String(outStrm.toByteArray()),
new String(errStrm.toByteArray()));
}
And it is triggered by either of the streams being too big for junit to handle. This is something to x-file with Ant, but there is also a root cause somewhere to deal with -what is creating 164MB worth of stdout or stderr?
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4721) OOM in .TestSetupAndCleanupFailure
Posted by "Ceki Gulcu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650591#action_12650591 ]
Ceki Gulcu commented on HADOOP-4721:
------------------------------------
Hello Steve,
Do you know the size of the buffer of FileAppender? Could you please provide your log4j.properties file?
> OOM in .TestSetupAndCleanupFailure
> ----------------------------------
>
> Key: HADOOP-4721
> URL: https://issues.apache.org/jira/browse/HADOOP-4721
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.0
> Environment: 64 bit linux with JRockit 64-bit JVM
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
>
> The root cause may be my lifecycle changes, but I'm seeing an OOM in TestSetupAndCleanupFailure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.