I believe that the parameters like heap size is only read at JVM initalizing phase. I guess one cannot change the heap size at run time. This prevents JVM from using up all of system's memories. <argLine>-Xmx1050m -XX:MaxPermSize=128M</argLine> is obviously ONLY for the forked JVM related spawned for surefire plugin. Jack
On Fri, Oct 3, 2008 at 5:14 PM, Martin Gainty <[EMAIL PROTECTED]> wrote: > > Good Evening Zhou- > fairly intuitive to see the new params acting as an initial configuration > for forked jvm's > > but admittedly cannot see how the jvm parameters such as what is identified > here > <argLine>-Xmx1050m -XX:MaxPermSize=128M</argLine>being used in the current > VM > > would be used to 'reconfigure' the current jvm process > > perhaps a JVM resource can elucidate > ? > Martin Gainty > ______________________________________________ > Disclaimer and confidentiality note > Everything in this e-mail and any attachments relates to the official > business of Sender. This transmission is of a confidential nature and Sender > does not endorse distribution to any party other than intended recipient. > Sender does not necessarily endorse content contained within this > transmission. > > > > Date: Fri, 3 Oct 2008 17:05:15 -0700 > > From: [EMAIL PROTECTED] > > To: [email protected] > > Subject: Re: mvn test phase out of memery issue > > > > Thanks, > > I will try that. Currently I am trying <forkMode>always</forkMode>. It > > works. But very very slow. We have over a thousand tests. > > Regards, > > Jack > > > > On Fri, Oct 3, 2008 at 4:15 PM, Matthew McCullough < > > [EMAIL PROTECTED]> wrote: > > > > > > > > You may need to increase the memory used by the surefire jvm if it is > set > > > to > > > fork. > > > > > > Here's a config example: > > > > > > <plugin> > > > <groupId>org.apache.maven.plugins</groupId> > > > <artifactId>maven-surefire-plugin</artifactId> > > > <version>2.3</version> > > > <configuration> > > > <includes> > > > <include>**/*Test.java</include> > > > </includes> > > > <forkMode>once</forkMode> > > > <!-- need more memory than the default for our unit > tests > > > --> > > > <argLine>-Xmx1050m -XX:MaxPermSize=128M</argLine> > > > </configuration> > > > </plugin> > > > > > > > > > > > > Jinyuan Zhou-3 wrote: > > > > > > > > Hello, > > > > When I run a test, (mvn test) out of memory happens when run one of > the > > > > unit > > > > test case methed : > > > > java.lang.OutOfMemoryError: Java heap space > > > > > > > > > > > > I did put the following . > > > > > > > > MAVEN_OPTS=-Xmx512m > > > > > > > > Can some one give a clue as which plugin is used in test phase, and > what > > > > option can be used to increase the heap size when running test? > > > > Thanks, > > > > Jack > > > > > > > > > > > > > > -- > > > View this message in context: > > > > http://www.nabble.com/mvn-test-phase-out-of-memery-issue-tp19805700p19807236.html > > > Sent from the Maven - Users mailing list archive at Nabble.com. > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > > > Some people lived like they will never die > > and died like they have never lived > > _________________________________________________________________ > Want to do more with Windows Live? Learn "10 hidden secrets" from Jamie. > > http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008 -- Some people lived like they will never die and died like they have never lived
