[Bug 3635] New: Feature Request: Option for JRE invocation to relaunch using the same JRE on Windows
bugzilla-daemon at icedtea.classpath.org
bugzilla-daemon at icedtea.classpath.org
Fri Oct 5 02:54:26 UTC 2018
https://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3635
Bug ID: 3635
Summary: Feature Request: Option for JRE invocation to relaunch
using the same JRE on Windows
Product: IcedTea-Web
Version: 1.7
Hardware: x86_64
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: NetX (javaws)
Assignee: jvanek at redhat.com
Reporter: martin.hickson at gmail.com
CC: unassigned at icedtea.classpath.org
Version: 1.7.1
It appears that if the heap size specified in the JNLP file is greater than the
current heap size then a new JRE process will be launched with the new heap
size.
When this is done, it appears that it will use the executable found on the PATH
to relaunch the JRE. Would it be possible to increase the configurability of
this so that it could optionally use the absolute path of the command that was
used to launch the first JRE to launch the second one?
This could be done by passing a system property through in the javaws.bat file
on the line that starts with %JAVA%, for example:
"%JAVA%" "-Djre.absolute.path=%JAVA%" -splash:%SPLASH_LOCATION%"
"%LAUNCHER_BOOTCLASSPATH%" %LAUNCHER_FLAGS% %JAVAWS_J_OPTIONS% "-classpath"
"%CP%" "-Dicedtea-web.bin.name=%PROGRAM_NAME%"
"-Dicedtea-web.bin.location=%BINARY_LOCATION%" "%CLASSNAME%" %ITW_WIN_SPECIALS%
%*
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20181005/c2072544/attachment.html>
More information about the distro-pkg-dev
mailing list