I am on JRE1.5. However I don't think I need more than 1GB. I think the problem is a bug in maven2.
We have run this code for months now on lots of Windows and OSX boxes running this with IntelliJ and Ant scripts. We have never needed more than 800m and typically 500m will do. With the MAVEN_OPTS setting I have tried 1.5GB and more (I only have 2GB physical memory) and still fails. Now I just retried a base component where 1GB was enough with maven a few days ago and now it is failing as well. Since the successful test I installed one snapshot release plugin but that shouldn't be an issue for test. I have no idea why one day maven will work but not the next but that has been my experience thus far with maven. I am at a loss for what to do...I may have to go back to Ant:( -dh -----Original Message----- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 5:52 PM To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError I've never seen an OOM where the VM specified which area ran out of space but I'm still stuck on 1.4, maybe 1.5 does this? And that would certainly lead me to think maybe you need even more than 1GB... -----Original Message----- From: Dave Hoffer [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 4:46 PM To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError Mike, Thanks, I did not know that. I set -XX:MaxPermSize=256m and got the same error. The error I get is: Exception in thread "Thread-1" java.lang.OutOfMemoryError: Java heap space Doesn't this mean that my OOM is the heap space which I have set as -Xmx1024m. -dh -----Original Message----- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 5:16 PM To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError 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] --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
