You need to understand something about the JVM memory system. Below you've configured the heap to be 1GB. Class data (.class) is stored in the permanant generation space which is different from the heap and defaults to 32MB in client and 64MB in server mode.
So you can give your JUnit tests 1TB if you want. If they load more than 32/64MB of class data, you will continue to get OOMs. There is a setting to increase this, I think it is -XX:PermGenSize=XXXm. It should work around the problem until you have a chance to upgrade to surefire 2.2. mike -----Original Message----- From: Dave Hoffer [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 3:35 PM To: Maven Users List Subject: [m2.0.4] OutOfMemoryError For some of my projects that use a lot of memory when running unit tests I set MAVEN_OPTS to -Xmx1024m to get all the tests to not throw OutOfMemoryErrors. I now have a maven project that has a dependency on the prior component but I do get an OutOfMemoryError when I run the unit tests. I have tried to set -Xmx to larger values with no success, as it always fails. The poms are all but identical, why should one fail? Also, in the process viewer I see that when running the tests there are two java processes. One reports using about 90MB and the other about 64MB. Why are there two? These numbers are way lower than the max java heap size specified. Any ideas? -dh --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
