Ant with JUnit task - OutOfMemoryError

Question

I have an interesting problem. I am using Ant which executes JUnit tests (test suite composed with 50 tests) via build.xml element. The problem is that I receive OutOfMemoryError.

I have enlarged heap space using ANT_OPTS arguments but it did not help. When I execute the same test suite in Eclipse - everything is fine - memory is released thanks to GC.

I think that this problem is related to Ant and its JUnit task.

Maybe logging of the tests are the reason(but on the other hand I have printsummary="false", [maybe outputtoformatters should be set to false as well???]).

My second guess is that TEST***.xml file (generated at the end of the test) is held in memory and flushed at the end of the test. Is there any way to reduce logs which are in that file?

Guys, please give me some clues.

Narrow down you problem. Start with just one junit test (comment out all the others) and see what happens. — draganstankovic, Aug 10 '12 at 20:07
When suite contains one test - everything is fine. Only big suites cause the problem. — Lucas Smith, Aug 10 '12 at 20:17
possible duplicate http://stackoverflow.com/questions/4182746/junitreport-ant-task-giving-java-lang-outofmemoryerror-java-heap-space — Pulak Agrawal, Aug 13 '12 at 03:27

score 1 · Answer 1 · answered Aug 10 '12 at 22:18

1

You need to set the maxmemory attribute in the junit task. See the Ant documentation.

answered Aug 10 '12 at 22:18

gareth_bowles

20,760
5
52
82

I've already tried it. maxmemory option works only when fork="true". It did not give any effect. Any more ideas? – Lucas Smith Aug 10 '12 at 23:09
Hmm - can you post the stack trace from the exception you're getting ? You might be running out of something other than heap space, such as PermGen space. – gareth_bowles Aug 11 '12 at 00:58
No, it is not PermGen. I have set the space of PermGen to the value of 256m. – Lucas Smith Aug 11 '12 at 07:19
1

OK - if you won't post the stack trace as everyone has asked, it's hard to help more. – gareth_bowles Aug 12 '12 at 22:48

score 1 · Accepted Answer · answered Sep 11 '12 at 12:27

1

to sum up I want to say that the root of the problems was logging. Logs were sent to the stream and not flushed. After switching the logs off - everything was fine.

answered Sep 11 '12 at 12:27

Lucas Smith

231
3
9

score 0 · Answer 3 · answered Aug 11 '12 at 03:05

0

By default the fork mode is off. Please try with fork mode on and forkmode set to pertest.

answered Aug 11 '12 at 03:05

Jayan

18,003
15
89
143

I think that it will not help. I have @Suite runner with 50 tests. Such a bunch is treated as a single test - one TEST-xxx.xml report file. I think that report generation will be performed within that forked JVM so it will give no effect. Any more ideas? – Lucas Smith Aug 11 '12 at 07:22
@ Lucas Smith : please post the final ant file content and exception stack trace. – Jayan Aug 11 '12 at 14:12

Ant with JUnit task - OutOfMemoryError

3 Answers3

Linked