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