JDK-6683047 : separate_jvm parameter should tear down target JVM more quickly
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-04-02
  • Updated: 2010-09-08
  • Resolved: 2008-06-27
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 6
6u10 b22Fixed
Related Reports
Relates :  
JDK-6627835 - Need a way to force an applet into its own JVM instance
Relates :  
JDK-6691244 - Conflicts between separate_jvm parameter and applet relaunches
Description
The new separate_jvm applet parameter (see 6627835) is very useful for isolating an applet into its own JVM instance. However, the JVM instances used to start up these applets still use the same timeout mechanism for tearing down the JVM instance once the applet has exited as is used for JVM instances that are allowed to launch more than one applet. We need to shut down the JVMs used to launch isolated applets more quickly.

This issue was raised on the Java Plug-In forum:

http://forums.java.net/jive/thread.jspa?threadID=38708&tstart=0
Comments
SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u10/6683047.0 testcase: http://j2se.east.sun.com/deployment/www/tests/1.6.0_10/6683047
03-04-2008
EVALUATION Added notion in the SetJVMIDMessage that the JVM has been started on behalf of a single applet using the separate_jvm parameter. Tear down JVM aggressively in PluginMain in this case to avoid both buildup of stale system tray icons on Windows and unnecessary prolonged resource consumption.
03-04-2008