Closed pgrinaway closed 10 years ago
I can confirm this issue:
-bash-4.1$ java -version
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
``
@csirving Also could we get Oracle HotSpot JVM installed, perhaps as a module?
@pgrinaway : Has this been resolved, or do we need @csirving to install?
I believe the limits on the head node (data or as) conflict with the default java heap size. A brief test confirms that is likely:
java -Xmx2000000 -version java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.11.90) (rhel-1.62.1.11.11.90.el6_4-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
This will be reviewed post move.
I see no module for Oracle HotSpot JVM. Please re-open as a new issue. Do not chain issues.
Yes this is a problem do the limits on the login node and java's default max heap size.
[root@mskcc-ln1 profile.d]# /usr/java/latest/bin/java -XX:+PrintFlagsFinal -version |grep -i HeapSize uintx ErgoHeapSizeLimit = 0 {product} uintx HeapSizePerGCThread = 87241520 {product} uintx InitialHeapSize := 2147483648 {product} uintx LargePageHeapSizeThreshold = 134217728 {product} uintx MaxHeapSize := 32126271488 {product} java version "1.7.0_25" Java(TM) SE Runtime Environment (build 1.7.0_25-b15) Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
Also the Oracle jre which includes the "HotSpot JVM" has been installed on the cluster since it was initially setup. I didn't realize openJDK was causing a conflict. You could solve this with a module for the Oracle jre but unless someone is particularly fond of openJDK, I for one am not, you could just jettison it.
[root@mskcc-ln1 /]# /usr/java/latest/bin/java -version java version "1.7.0_25" Java(TM) SE Runtime Environment (build 1.7.0_25-b15) Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
From: tatarsky notifications@github.com<mailto:notifications@github.com> Reply-To: cBio/cbio-cluster reply@reply.github.com<mailto:reply@reply.github.com> Date: Thu, 3 Jul 2014 10:03:50 -0700 To: cBio/cbio-cluster cbio-cluster@noreply.github.com<mailto:cbio-cluster@noreply.github.com> Cc: csirving cirving@sdsc.edu<mailto:cirving@sdsc.edu> Subject: Re: [cbio-cluster] Java is sometimes unhappy on the login node (#3)
I believe the limits on the head node (data or as) conflict with the default java heap size. A brief test confirms that is likely:
java -Xmx2000000 -version java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.11.90) (rhel-1.62.1.11.11.90.el6_4-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
This will be reviewed post move.
I see no module for Oracle HotSpot JVM. Please re-open as a new issue. Do not chain issues.
— Reply to this email directly or view it on GitHubhttps://github.com/cBio/cbio-cluster/issues/3#issuecomment-47956941.
We believe this is resolved or at least documented for workaround. If you agree, please close the issue.
Closing. Re-open if needed.
Attempting to get the version of Java with java -version yields
Additionally, I get a similar error trying to compile OpenMM on the login node:
I'm not sure if this is a Java configuration issue, though, since on the compute nodes it seems to work fine:
Does everyone else have this problem?