The JVM could not be started. The maximum heap size (-Xmx) might be too large

[BeDeBe]

Hi All,

We got the following issue when installing OpenWebStart via an SCCM task sequence. An SCCM application for OpenWebStart version 1.11.0 has been made and installs without any problems via Software Center. When installing the same application via a task sequence step, the application fails on devices with 32 Gb internal memory with the error in the installation log file "The JVM could not be started. The maximum heap size (-Xmx) might be too large".

The error in the task sequence is:
"The task sequence failed to install application Karakun OpenWebstart 1.11.0(ScopeId_25AD4020-6562-44AA-A5BD-4DEF05DF6E2C/Application_26caf670-3b70-4d8c-aaa1-ce09bca9306b) for action (Install Default Applications after restart) in the group () with exit code 16389. The operating system reported error 2147500037: Unspecified error"

On devices with 16 Gb internal memory we do not have any issues.

I found a similar topic from more than 1 year ago on this forum cf. viewtopic.php?t=8473 also indicating a difference on 16/32 Gb machines.

The installation command used is "OpenWebStart_windows-x64_1_11_0.exe -q -varfile response.varfile"
The response.varfile is used to set the installation path and lock certain settings for the end-user.

OpenWebStart version 1.9.1 has the same issue.

Any ideas how this could be solved? Is this a bug or some restriction of the installer?

Kind Regards

[Janak Mulani]

I am not familiar with SCCM.

The problem is while installing OWS using SCCM, not while running OWS to run a Jnlp file i.e. while executing the javaws command, right?

Which OWS installer are your using, 64 bit or 32 bit? How does SCCM invoke the OWS installer?

Did you check the I4J log that is generated when you run the installer? https://www.ej-technologies.com/resourc ... rrors.html

Did the solution mentioned at https://stackoverflow.com/questions/256 ... rted-error help?

[BeDeBe]

Hi Janak,

Thanks for your reply.

The problem is while installing OWS using SCCM, not while running OWS to run a Jnlp file i.e. while executing the javaws command, right?

Indeed, the problem exists only when running an automated installation during the task sequence using SCCM. There is no issue with OWS when using it once it could be installed e.g. by installing it after the task sequence has finished.

Which OWS installer are your using, 64 bit or 32 bit? How does SCCM invoke the OWS installer?

The OWS installer and the command used (like already mentioned) is "OpenWebStart_windows-x64_1_11_0.exe -q -varfile response.varfile". So, the 64-bit installer.

Did you check the I4J log that is generated when you run the installer? https://www.ej-technologies.com/resourc ... rrors.html

I do not have the complete log4j logfiles at this moment. The devices were restaged without OWS because they were needed.
I will try to get a 32 Gb machines for testing. They are bought for a specific reason and all in use. We only have 16 Gb machine in stock.
I only have a print screen taken during troubleshooting of the i4j_nlog_1.log which gives:
ERROR: could not initialize JVM
ERROR: Could not start JVM
-> but this is the same response as the response from the installer via the SCCM generated log.

Did the solution mentioned at https://stackoverflow.com/questions/256 ... rted-error help?

We are just using the installer which Karakun delivers. We cannot manipulate any settings in that installer.

[Janak Mulani]

Need to look at I4J logs to find out the problem.

[BeDeBe]

Hi Janak,

I finally succeeded to collect a new log file on a device. I cannot find more info in the i4j_nlog_1.log file. This is the only logfile created.
The only error message is "ERROR: could not initialize JVM" and "ERROR: Could not start JVM". After that the rollback is initiated.
I added the whole log as an attachment.

[1:173] Loading of JVM-DLL successful
[1:173] launching program
[1:173] adding options
[1:173] adding preconfigured modulepath
[1:173] entry
[1:173] entries 0
[1:173] adding preconfigured classpath
[1:173] entry
[1:173] entries 0
[1:173] vmoption count 9
[1:173] vmoption 0: -Dexe4j.semaphoreName=Local\c:_windows_ccmcache_13_files_openwebstart_windows-x64_1_11_0.exe
[1:173] vmoption 1: -Dexe4j.isInstall4j=true
[1:173] vmoption 2: -Dexe4j.moduleName=C:\Windows\ccmcache\13\Files\OpenWebStart_windows-x64_1_11_0.exe
[1:173] vmoption 3: -Dsun.java.command=C:\Windows\ccmcache\13\Files\OpenWebStart_windows-x64_1_11_0.exe
[1:173] vmoption 4: -Dexe4j.tempDir=C:\WINDOWS\TEMP\e4jA5FA.tmp_dir1734745183
[1:173] vmoption 5: -Dexe4j.unextractedPosition=46298112
[1:173] vmoption 6: -Djava.library.path=c:\windows\temp\e4ja5fa.tmp_dir1734745183\jre\bin;C:\WINDOWS\TEMP\e4jA5FA.tmp_dir1734745183\user;C:\WINDOWS\CCM\;C:\Program Files (x86)\Zulu\zulu-8-jre\bin\;C:\Program Files\Zulu\zulu-8-jre\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\WINDOWS\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps
[1:173] vmoption 7: -Dexe4j.consoleCodepage=cp0
[1:173] vmoption 8: -Djava.class.path=C:\WINDOWS\TEMP\e4jA5FA.tmp_dir1734745183\i4jruntime.jar;C:\WINDOWS\TEMP\e4jA5FA.tmp_dir1734745183\user.jar
[1:173] used stack size 0
[1:189] Creating JVM
[1:189] ERROR: could not initialize JVM
[1:189] ERROR: Could not start JVM
[1:189] deleting bundled jre C:\WINDOWS\TEMP\e4jA5FA.tmp_dir1734745183\jre

Kind regards.

P.S. FYI: ccmcache is the folder from which SCCM applications are started.

[Janak Mulani]

The OWS installer and the command used (like already mentioned) is "OpenWebStart_windows-x64_1_11_0.exe -q -varfile response.varfile". So, the 64-bit installer.

Just to confirm: you are installing in "unattended mode". The machine is a 64 bit windows machine, right?

When installing the same application via a task sequence step, the application fails on devices with 32 Gb internal memory with the error in the installation log file "The JVM could not be started. The maximum heap size (-Xmx) might be too large".

The problem is occurring only when OWS is being a installed via an SCCM Task Step. If you install the OWS on the same (32 GB) machine manually there is no problem with installation and subsequently starting aJnlp app with OWS. Right?

We are using Install4J to build the installer: "OpenWebStart_windows-x64_1_11_0.exe"

Here are the commandline options that can be used with the installer : https://www.ej-technologies.com/resourc ... tions.html

You could try some of the following commandline options with your command "OpenWebStart_windows-x64_1_11_0.exe -q ...":

-J-Xmx512m : try different values 256m, 128m, 64m which ever works
-Dinstall4j.debug=true : to
-Dinstall4j.detailStdout=true
-Dinstall4j.logToStderr=true
-temp <directory>