JDK-7032687 : Dragged-out applet can be closed when close browser
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-03-31
  • Updated: 2011-07-18
  • Resolved: 2011-05-31
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.
6u26-revFixed 7 b138Fixed
Related Reports
Relates :  
Follow up with CR7019614. A different cause can still cause dragged-out applet to be closed as the transport between client VM and server VM throws out IOException.

This is a regression. IOException is expected when browser is closed. The client VM should not exit unless there is no dragged-out applet hosting in the VM.

EVALUATION pipe and handleMessage can throw IOException cause the client VM to exit, which should not be the case. For pipe exceptions, it is very likely caused by browser closed, and we lost communication to browser anyway. Thus we should leave with only dragged-out applets running, which will then exit the VM when last instance of dragged-out applet closed through the DragListener interface. For other IOException, it is better leave the loop, and let the caller decide what is appropriate operation.