JDK-6741370 : -Xmx ignored in control panel if java_arguments parameter is specified
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2008-08-26
  • Updated: 2011-02-16
  • Resolved: 2008-10-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6u10 b32Fixed
Related Reports
Relates :  
JDK-6737531 - Runtime parameters in Java Control Panel is not preserved when jre version has milestone appended.
Description
FULL PRODUCT VERSION :
Java(TM) SE Runtime Environment (build 1.6.0_10-b28)

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]

A DESCRIPTION OF THE PROBLEM :
If I use the java_arguments parameter with -Djnlp.packEnabled=true, say, the setting for -Xmx in the Java control panel is ignored, leading to 64M being used


REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
Have to specify the -Xmx in the java_arguments parameter
Comments
WORK AROUND If java_arguments is set in html, please also set the desired -Xmx in java_arguments. Even -Xmx is not set in java_arguments, it has the implicit default value of 64m.
27-08-2008
EVALUATION ok, we now know the root cause. When java_arguments is specified, the max heap (-Xmx) of java_arguments set is implicitly set to be 64m. The algorithm that merges java_arguments set and parameters set from control panel propagates the max heap from the java_arguments because the arguments set is non-default (the parameters from control panel is considerred to be default. We let non-default win over default). And we deliberately let java_arguments win over control panel because this provides more flexiblity to control jvm parameters for each applet. We need more thought on this max heap propagation.
27-08-2008
EVALUATION Tested with 6u10 b30. The runtime parameters in control panel is preserved. So this bug is not duplicate of 6737531. The above evaluation was from a test runing without java_arguments specified in the applet html file, the runtime parameters from the java control panel are used. If bothe are specified, the parameters from the java control panel are used in the attached java process except for "-Xmx". Other parameters from the control panel are used fine along with arguments from java_arguments.
26-08-2008
EVALUATION ###@###.### indicates this is not reproducible with the latest 6u10 build 30. Marking incomplete and contacting customer before closing as not reproducible.
26-08-2008