JDK-7006185 : DnD: showStatus and showDocument calls fail from dragged out applet
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: generic
  • Submitted: 2010-12-10
  • Updated: 2011-05-17
  • Resolved: 2011-05-17
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 7
7 b135Fixed
Related Reports
Relates :  
JDK-7019614 - Sometimes when cloing the browser after applet is dragged out of browser, applet will also be closed
Description
Tested build : jdk7-b121
showDocument when called from dragged out applet should open page inside the default browser window and showStatus should print out the given text inside the Java console. But that's not happening with promoted jdkb-121. With promoted bits it's failing silently but with nighlty bits following exceptions is getting thrown when these APIs are called:
java.io.IOException: Error 232 writing to named pipe, numWritten 0, WriteFile ts: 4494344968437, now ts: 4494344968458, dT 21
	at sun.plugin2.ipc.windows.WindowsNamedPipe.write(Unknown Source)
	at sun.plugin2.message.transport.NamedPipeTransport$SerializerImpl.flush(Unknown Source)
	at sun.plugin2.message.transport.NamedPipeTransport$SerializerImpl.writeByte(Unknown Source)
	at sun.plugin2.message.AbstractSerializer.writeInt(Unknown Source)
	at sun.plugin2.message.AppletMessage.writeFields(Unknown Source)
	at sun.plugin2.message.ShowStatusMessage.writeFields(Unknown Source)
	at sun.plugin2.message.transport.SerializingTransport.write(Unknown Source)
	at sun.plugin2.message.Pipe.send(Unknown Source)
	at sun.plugin2.main.client.MessagePassingExecutionContext.showStatus(Unknown Source)
	at sun.plugin2.applet2.Plugin2Host.showStatus(Unknown Source)
	at com.sun.deploy.uitoolkit.impl.awt.AWTAppletAdapter$AppletContextImpl.showStatus(Unknown Source)
	at DragExample$1$2.actionPerformed(DragExample.java:176)
	at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
	at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
	at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
	at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
	at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
	at java.awt.Component.processMouseEvent(Unknown Source)
	at javax.swing.JComponent.processMouseEvent(Unknown Source)
	at java.awt.Component.processEvent(Unknown Source)
	at java.awt.Container.processEvent(Unknown Source)
	at java.awt.Component.dispatchEventImpl(Unknown Source)
	at java.awt.Container.dispatchEventImpl(Unknown Source)
	at java.awt.Component.dispatchEvent(Unknown Source)
	at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
	at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
	at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
	at java.awt.Container.dispatchEventImpl(Unknown Source)
	at java.awt.Component.dispatchEvent(Unknown Source)
	at java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.run(Unknown Source)

Steps to reproduce:
1) Try to load the following applet inside the IE browser (due to open swing applet issue do not try this scenario inside FF browser)
http://sqeweb.sfbay.sun.com/deployment2/jitu/latest_ws_test/6/deployment/src/plugin/DnD/DnD/html/DragExample.html
2) Drag applet out of browser and do a page reload.
3) Close the browser and try to click on "Reopen web page" and "Show Applet Status"
If you are able to see above mentioned behavior then bug is reproduced
Comments
EVALUATION Close the browser breaks the existing communication channel between the client VM and server VM, thus should cause an update of the Applet2Host for the drag-out applet.
16-03-2011