JDK-6839727 : java plugin should avoid relaunch of jvm if possible
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u16
  • Priority: P3
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: windows
  • CPU: x86
  • Submitted: 2009-05-11
  • Updated: 2013-11-01
  • Resolved: 2012-03-20
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
6-poolResolved
Related Reports
Relates :  
JDK-6799345 - JFC demos threw exception in the Java Console when applets are closed
Relates :  
JDK-6627356 - Try to preserve Lock invariants even when faced with Thread.stop
Relates :  
JDK-6878284 - Sometimes test/javax/swing/system/6799345/TestShutdown.java "hangs"
Relates :  
JDK-6874336 - jnlp.packEnabled and jnlp.versionEnabled should not cause any JVM relaunch
Description
reqest from performance team

when we try to reload applets, sometimes the jvm are relaunched, even if the jvm parameters matches.  (or even just refresh on the current running applet page)

this might be caused by jvm bug:

6627356 Try to preserve Lock invariants even when faced with Thread.stop  

since we don't know when the jvm bug will be fixed, 
we should investigate and see if this can be workaround in the java plugin
Comments
EVALUATION I do not think this problem is applicable to JRE7/8. At least not in this form and we have other CRs to improve relaunch logic.
20-03-2012
EVALUATION Effect of problem described in the 6627356 can be reduced if use of concurrent classes in the areas of library/deploy/fx code will be more correct. For example, it appears (just from reading some of the related CR's) that swing causes many of these exceptions, specifically javax.swing.TimerQueue and SwingWorker. Therefore, we consider backporting fixes for 6799345 and 6878284 to 6 updates. Note that preliminary tests with repeated reload still provoke JVM restarts (using Flickr Client applet restart is usually happening every 5 times). Perhaps it happens a bit less frequently but this clearly is not the only reason. Also, repeating reload sometimes causes OOM. We likely have memory leak somewhere in the plugin code too.
03-09-2009