You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by Kevin Meyer - KMZ <ke...@kmz.co.za> on 2010/10/21 20:41:47 UTC

MAVEN_OPTS?

What MAVEN_OPTS are you using to allow a successful "mvn clean 
install" from trunk?

I've been nudging up the values, but I now get a:
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at 
pc=0x6d98c511, pid=1988, tid=1688
#
# JRE version: 6.0_17-b04
# Java VM: Java HotSpot(TM) Client VM (14.3-b01 mixed mode 
windows-x86 )
# Problematic frame:
# V  [jvm.dll+0xdc511]
#
# An error report file with more information is saved as:
# K:\Dev\NAKEDO~1\isis\trunk\hs_err_pid1988.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp



Re: MAVEN_OPTS?

Posted by Kevin Meyer - KMZ <ke...@kmz.co.za>.
> On 21/10/2010 19:41, Kevin Meyer - KMZ wrote:
> > What MAVEN_OPTS are you using to allow a successful "mvn clean
> > install" from trunk?

I've just had "mvn -o clean install" success with[1]:
-Xms512m -Xmx1024m -XX:MaxPermSize=512m 
-XX:+UseConcMarkSweepGC 
-XX:+CMSPermGenSweepingEnabled 
-XX:+CMSClassUnloadingEnabled

It leaves a message "Please use CMSClassUnloadingEnabled in 
place of CMSPermGenSweepingEnabled in the future", which I'll test 
next time.

Regards,
Kevin

[1] http://maven.40175.n5.nabble.com/java-lang-OutOfMemoryError-
PermGen-space-problem-td119135.html

Re: MAVEN_OPTS?

Posted by Alexander Krasnukhin <th...@gmail.com>.
You could try using lower -Xms & -Xmx values e.g. 128m & 900m. One time it
helped me in the similar situation.

On Thu, Oct 21, 2010 at 9:02 PM, Kevin Meyer - KMZ <ke...@kmz.co.za> wrote:

> On 21 Oct 2010 at 19:48, Dan Haywood wrote:
>
> > Yuk.
> >
> > I've been using -Xms512m -Xmx1024m on Maven 2.2.1.
> >
> > That looks like a bug in the JVM, perhaps.  However, you aren't on the
> > latest release, which is 6.0_22, I think.  Upgrade that first then see.
> > I haven't had any probs on 1.6_021.
>
> I'll have a go later. Shutting down for the evening.
>
> >
> > What's the OS?  I'm on Win7 64bit.
>
> Don't laugh: I'm using trusty Win2k. This is why I love Eclipse (Helios)
> and java - it is still useable on my home system - unlike Visual Studo
> 10 (sorry Richard)!
>
> If I don't include "clean", the install works fine. Next time I'll try
> breaking that up into two steps...
>
>
> Regards,
> Kevin
>
>
>


-- 
Regards,
Alexander

Re: MAVEN_OPTS?

Posted by Kevin Meyer - KMZ <ke...@kmz.co.za>.
On 21 Oct 2010 at 19:48, Dan Haywood wrote:

> Yuk.
> 
> I've been using -Xms512m -Xmx1024m on Maven 2.2.1.
> 
> That looks like a bug in the JVM, perhaps.  However, you aren't on the 
> latest release, which is 6.0_22, I think.  Upgrade that first then see.  
> I haven't had any probs on 1.6_021.

I'll have a go later. Shutting down for the evening.

> 
> What's the OS?  I'm on Win7 64bit.

Don't laugh: I'm using trusty Win2k. This is why I love Eclipse (Helios) 
and java - it is still useable on my home system - unlike Visual Studo 
10 (sorry Richard)!

If I don't include "clean", the install works fine. Next time I'll try 
breaking that up into two steps...


Regards,
Kevin



Re: MAVEN_OPTS?

Posted by Dan Haywood <dk...@gmail.com>.
Yuk.

I've been using -Xms512m -Xmx1024m on Maven 2.2.1.

That looks like a bug in the JVM, perhaps.  However, you aren't on the 
latest release, which is 6.0_22, I think.  Upgrade that first then see.  
I haven't had any probs on 1.6_021.

What's the OS?  I'm on Win7 64bit.

---
BTW, I also have started building on Maven 3.0.  Seems to work fine so far.

It also has the option to build in parallel; when I did so I had to up 
the memory (to -Xmx2048m).  Running with 8 threads (2 per core) was a 
bit faster, but not much (~20%).  I guess I'm maxing out on the disks.

Dan


On 21/10/2010 19:41, Kevin Meyer - KMZ wrote:
> What MAVEN_OPTS are you using to allow a successful "mvn clean
> install" from trunk?
>
> I've been nudging up the values, but I now get a:
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at
> pc=0x6d98c511, pid=1988, tid=1688
> #
> # JRE version: 6.0_17-b04
> # Java VM: Java HotSpot(TM) Client VM (14.3-b01 mixed mode
> windows-x86 )
> # Problematic frame:
> # V  [jvm.dll+0xdc511]
> #
> # An error report file with more information is saved as:
> # K:\Dev\NAKEDO~1\isis\trunk\hs_err_pid1988.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
>
>
>