OutOfMemoryError while executing JUnit Test cases with maven install

[Pratik Surti]

Hi All,

I am executing more than 1,000 Junit test cases using TestSuits together in one shot. In order to execute these test cases as Junit, it is working fine but when executing it as the maven install, it is throwing OutOfMemoryError at almost after the count of 150.

I tried to maximize jvm heap size but the problem persisted.

After I found another solution updating the configuration details in POM.xml as below:

<plugin>

 <groupId>org.apache.maven.plugins</groupId>

 <artifactId>maven-surefire-plugin</artifactId>

   <configuration>

    <forkMode>pertest</forkMode>

    <argLine>-Xms512m -Xmx1024m</argLine>

    <testFailureIgnore>false</testFailureIgnore>

</configuration>

</plugin>

After doing this I am able to execute all the JUnit test cases without having and OutOfMemoryError but performance got degraded. I want to know:

1) How can I improve the performance ?
1) Is changes mentioned above in POM.xml are OK ?
2) Can we mentioned the memory allocation in POM.xml like the way mentioned above ?

Best Regards,
Pratik

[David Newton]

I don't see anything wrong with what you did (although I've always just specified the args on the command line). Still, if you're running out of memory after 150 tests, I'd make sure your tests are releasing whatever they're using, because that seems kind of extreme. As a counter-example, I have a project that has thousands of tests, and it makes it through the bulk of them before throwing an OOME.

[Karl Heinz Marbaise]

Hi,

have you checked the Maven settings for the JVM itself ?

Kind regards
Karl Heinz Marbaise

[Pratik Surti]

Yes I have managed to change the settings for maven jvm heap size.

After doing the changes in POM.xml, OutOfMemoryError is resolved. Only issue with performance.

It takes 34 minutes to successfully execute 1,117 Junit test cases with Maven. Running it normally through Eclipse Junit, it takes around 15 minutes.

Is there any chance of having multiple object references not released after the execution ?

[David Newton]

Are you sure you want to fork per test? (Which as far as I know is for backwards compatibility, as per the docs.) I'd try that to see what the difference is.

[Pratik Surti]

if this is the case of backward compatibility then my junit test case do not have dependency on each other, as they are independent of execution.

Which approach shall I try instead of fork per test ?

[David Newton]

*Maven* backwards compatibility. I don't know, the default of "once"?

[Pratik Surti]

Let me try with"once". I will update in some time.

[Pratik Surti]

Hi Good to see the performance improvement as below. It has now taken 10 minutes.

    
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10 minutes 29 seconds
[INFO] Finished at: Wed Mar 24 18:15:52 IST 2010
[INFO] Final Memory: 2M/23M
[INFO] ------------------------------------------------------------------------