JDK-6691244 : Conflicts between separate_jvm parameter and applet relaunches
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-04-20
  • Updated: 2010-09-08
  • Resolved: 2008-05-22
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 b23Fixed
Related Reports
Relates :  
Description
A customer (see Comments for contact details) provided a test case that shows that the recent fix for 6683047 (separate_jvm parameter should tear down target JVM more quickly) is conflicting with the applet relaunch mechanism. The attached JVM is tearing itself immediately after sending the applet relaunch message back to the browser and the browser side never gets a chance to process it. The code needs to be changed so that the browser side is responsible for tearing down the attached JVM in the case where the attached JVM was for a particular applet and it also caused an applet relaunch.

Comments
EVALUATION The fix for 6683047 (separate_jvm parameter should tear down target JVM more quickly) introduced a conflict with the applet relaunch mechanism. To resolve it, the attached JVM needs to keep track of whether an applet relaunch occurred, and if so, then if it is an exclusive JVM instance, then the browser side assumes responsibility for tearing it down. Tested with the customer's test case. No test case right now due to severe time constraints.
21-04-2008

SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u10/6691244.0
21-04-2008