| Re: [che-dev] OoM in mvn clean install |
Yes. Not good?
However, 32bit does not work either, it just stops a bit further down the road.
BTW, MAVEN_OPTS are apparently not passed to the java executable. It always runs with -Xss512m -Xmx2048m -XX:MaxPermSize=1024m, see last line:
…
[INFO] --- maven-antrun-plugin:1.8:run (buildnumber) @ assembly-ide ---
[WARNING] Parameter tasks is deprecated, use target instead
[INFO] Executing tasks
main:
[INFO] Executed tasks
[INFO]
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ assembly-ide ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /mnt/sdb1/che/che/assembly-ide/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.3:testCompile (default-testCompile) @ assembly-ide ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ assembly-ide ---
[INFO] No tests to run.
[INFO]
[INFO] --- gwt-maven-plugin:2.7.0:compile (default) @ assembly-ide ---
[INFO] Error occurred during initialization of VM
[INFO] java.lang.OutOfMemoryError: unable to create new native thread
[INFO] at java.lang.Thread.start0(Native Method)
[INFO] at java.lang.Thread.start(Thread.java:714)
[INFO] at java.lang.ref.Reference.<clinit>(Reference.java:162)
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Che SDK :: Parent .................................. SUCCESS [ 1.746 s]
[INFO] Che SDK :: Compiling GWT Application ............... FAILURE [ 10.663 s]
[INFO] Che SDK :: Platform API ............................ SKIPPED
[INFO] Che SDK :: Code Assistant :: Packaging ............. SKIPPED
[INFO] Che SDK :: Assemblies Tomcat ....................... SKIPPED
[INFO] Che SDK :: QA ...................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13.250 s
[INFO] Finished at: 2015-04-09T14:22:11+02:00
[INFO] Final Memory: 48M/377M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.7.0:compile (default) on project assembly-ide: Command [[
[ERROR] /bin/sh -c '/usr/java/32/jdk1.7.0_75/jre/bin/java' '-Xss512m' '-Xmx2048m' '-XX:MaxPermSize=1024m' …
From: che-dev-bounces@xxxxxxxxxxx [mailto:che-dev-bounces@xxxxxxxxxxx] On Behalf Of Sergii Kabashniuk
Sent: Donnerstag, 9. April 2015 13:45
To: che developer discussions
Subject: Re: [che-dev] OoM in mvn clean install
JVM 64bit?
On Thu, Apr 9, 2015 at 2:36 PM, Pohl, Christoph <christoph.pohl@xxxxxxx> wrote:
Hi Sergii,
thanks, but I already tried different MAVEN_OPTS, unfortunately to no avail. Even decreasing the stack size to a minimum of 228kB did not solve the issue:
export MAVEN_OPTS="-Xmx3G -XX:MaxPermSize=1G -Xss228k"
My box has a total of 8G RAM and 4G swap space, which usually suffice for a 3G JVM.
Any other ideas or suggestions?
Thanks,
Christoph
From: che-dev-bounces@xxxxxxxxxxx [mailto:che-dev-bounces@xxxxxxxxxxx] On Behalf Of Sergii Kabashniuk
Sent: Donnerstag, 9. April 2015 11:10
To: che developer discussions
Subject: Re: [che-dev] OoM in mvn clean install
Hello
Is this help?export "MAVEN_OPTS=-Xmx2G -XX:MaxPermSize=512m"
How much memory do you have?
Sergii Kabashniuk
On Thu, Apr 9, 2015 at 11:48 AM, Pohl, Christoph <christoph.pohl@xxxxxxx> wrote:
Hi all,
I am struggling with a clean build of che 3.9.0-SNAPSHOT from https://github.com/codenvy/che.git on a SLES11 box with Maven 3.3.1 and Oracle JDK 1.7.0_75.
It dies while “Invoking generator com.google.gwt.resources.rebind.context.InlineClientBundleGenerator” after all the resolveResource calls for the svg images with the following exception:
[INFO] Compiling 4 permutations
[ERROR] Exception in thread "main" java.lang.OutOfMemoryError: unable to create new native thread
[ERROR] at java.lang.Thread.start0(Native Method)
[ERROR] at java.lang.Thread.start(Thread.java:714)
[ERROR] at com.google.gwt.dev.ExternalPermutationWorkerFactory.launchExternalWorker(ExternalPermutationWorkerFactory.java:311)
[ERROR] at com.google.gwt.dev.ExternalPermutationWorkerFactory.getWorkers(ExternalPermutationWorkerFactory.java:373)
[ERROR] at com.google.gwt.dev.PermutationWorkerFactory.createWorkers(PermutationWorkerFactory.java:365)
[ERROR] at com.google.gwt.dev.PermutationWorkerFactory.compilePermutations(PermutationWorkerFactory.java:267)
[ERROR] at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:211)
[ERROR] at com.google.gwt.dev.Compiler.run(Compiler.java:221)
[ERROR] at com.google.gwt.dev.Compiler.run(Compiler.java:158)
[ERROR] at com.google.gwt.dev.Compiler$1.run(Compiler.java:120)
[ERROR] at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55)
[ERROR] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)
[ERROR] at com.google.gwt.dev.Compiler.main(Compiler.java:127)
Normally, this hints at a too restrictive max number of fork processes. But “ulimit -u" gives 62748 for my user. More than enough I guess.
No more luck with different versions of Maven or Java. I was not able to reproduce this on Windows, though.
Did anybody experience similar issues recently?
Cheers,
Christoph
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev