JDK-7085149 : Local JVM settings should not cause relaunch unless conflict is detected.
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-08-30
  • Updated: 2011-09-22
  • Resolved: 2011-09-06
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 7 JDK 8
7u2 b04Fixed 8Fixed
Description
Originally reported at http://javafx-jira.kenai.com/browse/RT-14030.

Local setting is usually set for diagnosis purpose, and is always honored as that is set on local system. Relaunch client VM because of those setting is not necessary unless there is a conflict on setting.
Comments
EVALUATION The issue is mainly that at client VM, trusted arguments should be considered as default setting because it should always be honored. In case target app has specific request, then we should detect if there is a conflict.
30-08-2011