P3
FULL PRODUCT VERSION :
JRE 1.6u10
ADDITIONAL OS VERSION INFORMATION :
Windows XP SP3
EXTRA RELEVANT SYSTEM CONFIGURATION :
Web browser: Mozilla Firefox 3.0.5
A DESCRIPTION OF THE PROBLEM :
This problem is described and discussed here:
http://forums.java.net/jive/thread.jspa?messageID=327760
JVM Parameters like -Xdebug or -Xmx are not passed to a applet VM under certain conditions with Java Plugin 2:
1. the applet is launched by Java Web Start / a JNLP file
("jnlp_href" parameter with an external jnlp file)
2. the applet is launched in a web browser (Firefox), not with JavaWS in a command line
3. the JVM parameters are configured in the JNLP file
(like <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se" java-vm-args="-Xmx256m -Xdebug"/>)
4. the applet is runnig in a seperate JVM
(this can either be forced by the "separate_jvm" switch or the 2nd VM is started automatically with certain configurations)
In these cases the JVM parameters are passed to the JavaWS launcher VM, but not to the second ("separate") VM that is initiated by JavaWS. This can be seen by typing S in the plugin console:
javaplugin.vm.options=
No parameters are set in the applet.
Configuring applet JVM parameters in the control panel also does NOT help. These parameters seem to be completely ignored if an applet has been run with Java Web Start (maybe this is also bug :-/ ?).
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
(see description)
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
All JVM parameters specified in the JNLP file are passed to the actual JVM process, also if a second process is started. This should work for all standard switches like -Xmx or -Xdebug, even if the JNLP is NOT signed.
See also here: https://jdk6.dev.java.net/plugin2/jnlp/#COMMAND_LINE_ARGS
And here: http://java.sun.com/javase/6/docs/technotes/guides/javaws/developersguide/syntax.html#resources
ACTUAL -
(see description)
ERROR MESSAGES/STACK TRACES THAT OCCUR :
(none)
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
WORKAROUNDs:
1. Dont use a seperate JVM, or (if a seperate JVM is automatically started) dont use JNLP. Then all parameters are passed correctly to the ONLY started JVM in the same way as they are passed to the JavaWS VM anyway.
OR
2. Use the legacy Java Plugin (this can be set in the control panel)
Both ways work perfectly to pass the JVM parameters but none of the additional JNLP options can be used if an applets isnt started by JNLP or by the new Java Plugin.
JRE 1.6u10
ADDITIONAL OS VERSION INFORMATION :
Windows XP SP3
EXTRA RELEVANT SYSTEM CONFIGURATION :
Web browser: Mozilla Firefox 3.0.5
A DESCRIPTION OF THE PROBLEM :
This problem is described and discussed here:
http://forums.java.net/jive/thread.jspa?messageID=327760
JVM Parameters like -Xdebug or -Xmx are not passed to a applet VM under certain conditions with Java Plugin 2:
1. the applet is launched by Java Web Start / a JNLP file
("jnlp_href" parameter with an external jnlp file)
2. the applet is launched in a web browser (Firefox), not with JavaWS in a command line
3. the JVM parameters are configured in the JNLP file
(like <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se" java-vm-args="-Xmx256m -Xdebug"/>)
4. the applet is runnig in a seperate JVM
(this can either be forced by the "separate_jvm" switch or the 2nd VM is started automatically with certain configurations)
In these cases the JVM parameters are passed to the JavaWS launcher VM, but not to the second ("separate") VM that is initiated by JavaWS. This can be seen by typing S in the plugin console:
javaplugin.vm.options=
No parameters are set in the applet.
Configuring applet JVM parameters in the control panel also does NOT help. These parameters seem to be completely ignored if an applet has been run with Java Web Start (maybe this is also bug :-/ ?).
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
(see description)
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
All JVM parameters specified in the JNLP file are passed to the actual JVM process, also if a second process is started. This should work for all standard switches like -Xmx or -Xdebug, even if the JNLP is NOT signed.
See also here: https://jdk6.dev.java.net/plugin2/jnlp/#COMMAND_LINE_ARGS
And here: http://java.sun.com/javase/6/docs/technotes/guides/javaws/developersguide/syntax.html#resources
ACTUAL -
(see description)
ERROR MESSAGES/STACK TRACES THAT OCCUR :
(none)
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
WORKAROUNDs:
1. Dont use a seperate JVM, or (if a seperate JVM is automatically started) dont use JNLP. Then all parameters are passed correctly to the ONLY started JVM in the same way as they are passed to the JavaWS VM anyway.
OR
2. Use the legacy Java Plugin (this can be set in the control panel)
Both ways work perfectly to pass the JVM parameters but none of the additional JNLP options can be used if an applets isnt started by JNLP or by the new Java Plugin.