Bug ID: JDK-7071801 javafx2 application (browser or webstart) running in sandbox missing exitVM/stopThread permission

Type: Bug
Component: deploy
Sub-Component: deployment_toolkit
Affected Version: 7-client

Priority: P2
Status: Closed
Resolution: Duplicate
OS: windows
CPU: x86

Submitted: 2011-07-27
Updated: 2011-08-06
Resolved: 2011-08-06

Versions (Unresolved/Resolved/Fixed)

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
7-clientResolved

javafx2 application (browser or webstart) running in sandbox missing exitVM/stopThread permission

this is because in AppPolicy.addSandboxPermissionsObject, currently we have code:

  if (JNLPClassLoaderUtil.getInstance() instanceof JNLPClassLoader) {
            perms.add(new RuntimePermission("exitVM"));
            perms.add(new RuntimePermission("stopThread"));
        }

When running with FX2 application - this check might fail.  If it's the JavaFX application thread, the thread's context class loader will either be the bootclassloader, or just a vanila URLClassLoader.  It won't be instanceof JNLPClassLoaderIf.   And it will not be instanceof JNLPClassLoader either - because FX2 applications will always be loaded by JNLP2ClassLoader now.

I believe it's okay to grant these 2 permissions for FX2 sandbox application always - because FX2 applications will always run in it's own JVM, no matter it's browser based or webstart.  (similar to awt webstart application)  There is no sharing of JVM between FX2 applications for now.