JDK-7058119 : -Xmx is not recognized as running JVM parameter in javaws after relaunch
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-06-22
  • Updated: 2011-09-22
  • Resolved: 2011-08-17
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.
7u2 b03Fixed 8Fixed
This is originally reported at http://javafx-jira.kenai.com/browse/RT-14030.

During the investigation, we found that there is a second attempt to relaunch which should not be happening, and the cause for that is the -Xmx setting is not recognized although is effective in current running JVM.

SUGGESTED FIX Make sure we pass along the -Xms setting, and review the policy and implementation on conflict resolution.

EVALUATION Since the second relaunch attempt is ignored, and current running JVM indeed has the setting, this is not critical and the application will be running with desired heap size setting. However, this brings up a bigger question how conflict between local options specified via javaws and the options specified in JNLP should be resolved.