JDK-6663106 : JNLP applet re-launch freezes FF3 due to pending LiveConnect messages
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-02-14
  • Updated: 2010-09-08
  • Resolved: 2008-03-25
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 b13Fixed
Related Reports
Relates :  
JDK-6706305 - JavaScript -> Java calls are being allowed against the applet too early
Relates :  
JDK-6727020 - Intermittent reliability problems related to applet relaunching
Relates :  
JDK-6742814 - In Java to JavaScript communication, JSObject.getWindow().call() locks up IE
Description
JNLP applet re-launch freezes FF3 due to pending LiveConnect messages.

The browser waits for the LiveConnect response forever,
since the messages were received by the 1st JNLP applet client,
which never respons due to relaunch.
Comments
SUGGESTED FIX webrev: http://sa.sfbay.sun.com/projects/deployment_data/6u10/6663106.1 testcase: http://j2se.east.sun.com/deployment/www/tests/1.6.0_10/6663106/
04-09-2008
SUGGESTED FIX Fix as suggested before :)
15-02-2008
SUGGESTED FIX The LiveConnect messages must be re-send to the client JVM, so it can properly respond to the browser.
14-02-2008
EVALUATION FF3 will freeze after relaunch an applet.
14-02-2008