United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6683047 separate_jvm parameter should tear down target JVM more quickly
6683047 : separate_jvm parameter should tear down target JVM more quickly

Details
Type:
Bug
Submit Date:
2008-04-02
Status:
Closed
Updated Date:
2010-09-08
Project Name:
JDK
Resolved Date:
2008-06-27
Component:
deploy
OS:
generic
Sub-Component:
plugin
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
6u10
Fixed Versions:
6u10

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

Sub Tasks

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
2008-04-03 
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.
2008-04-03


Hardware and Software, Engineered to Work Together