JDK-6737531 : Runtime parameters in Java Control Panel is not preserved when jre version has milestone appended.
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows,windows_xp
  • CPU: generic,x86
  • Submitted: 2008-08-15
  • Updated: 2010-09-08
  • 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.
6u10 b31Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
When jre version has milestone appended, for example, "1.6.0_10-beta", "1.6.0_10-rc", jre runtime parameters entered in java control panel are not preserved. They are lost when refresh jre list.

To reproduce it, install 1.6.0_10 rc. Check output of "java -version" to make sure the version string has "-rc" in it. And open JCP java panel, make sure the "1.6.0_10-rc" is listed. Enter jvm parameter for "1.6.0_10-rc" in JCP, for example "-Dsun.java2d.noddraw=true". Save it and close JCP. Open JCP again, look the java panel, the jvm parameter is not there.

This is not reproducible if jre version is "1.6.0_10".

EVALUATION The root cause is the java webstart native launcher. In java control panel, it calls javaws.exe to scan registry to find new updated jres in the Java panel. The jre prodcut version obtained from windows registry does not contain milestones. javaws.exe considers the jre from the registry (1.6.0_10) is different from the one from the deployment configuration file (which is 1.6.0_10-rc). So it update the configuartion file with the one from the registry. However, it does not merge the vm arguments from the configuaration file. We can fix it in javaws.exe by only comparing the product version without milestones.

EVALUATION The bug affects many many developers who use "beta" "rc" version of java plugins.