United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6627835 Need a way to force an applet into its own JVM instance
JDK-6627835 : Need a way to force an applet into its own JVM instance

Details
Type:
Enhancement
Submit Date:
2007-11-09
Status:
Closed
Updated Date:
2010-09-08
Project Name:
JDK
Resolved Date:
2008-06-13
Component:
deploy
OS:
generic
Sub-Component:
plugin
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
6u10
Fixed Versions:
6u10 (b13)

Related Reports
Backport:
Relates:

Sub Tasks

Description
In a discussion with a customer about the new Java Plug-In, a mechanism for forcing an individual applet into its own JVM instance was requested. While specifying JVM command-line arguments such as -Xmx will increase the chances of an applet getting its own JVM instance, there might be situations where a given applet really doesn't want to run in the same JVM with any others. This is a simple change to make so we should try to support it in the initial release.

                                    

Comments
EVALUATION

Adding support of forcing an applet into its own JVM instance via the applet 
html parameter as follows:

     <PARAM NAME="separate_jvm" VALUE="true"></PARAM>

The fix also adds an "exclusive" flag to the JVMInstance.
When the "exclusive" flag is set, that particular JVMInstance won't be used by 
other applets.
                                     
2008-02-07
SUGGESTED FIX

http://sa.sfbay.sun.com/projects/deployment_data/6u10/6627835.1
                                     
2008-02-07



Hardware and Software, Engineered to Work Together