United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-7058119 -Xmx is not recognized as running JVM parameter in javaws after relaunch
JDK-7058119 : -Xmx is not recognized as running JVM parameter in javaws after relaunch

Details
Type:
Bug
Submit Date:
2011-06-22
Status:
Resolved
Updated Date:
2011-09-22
Project Name:
JDK
Resolved Date:
2011-08-17
Component:
deploy
OS:
generic
Sub-Component:
deployment_toolkit
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
7
Fixed Versions:
7u2 (b03)

Related Reports
Backport:

Sub Tasks

Description
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.

                                    

Comments
SUGGESTED FIX

Make sure we pass along the -Xms setting, and review the policy and implementation on conflict resolution.
                                     
2011-06-22
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.
                                     
2011-06-22



Hardware and Software, Engineered to Work Together