JDK-6659803 : Unable to close the Java Console when applet is launched using old plugin for PIT build 6u10-b12
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2008-02-06
  • Updated: 2010-04-04
  • Resolved: 2008-02-13
Related Reports
Duplicate :  
Description
After loading an applet, it is not possible to close the Java Console

Points : 
a) This bug is producible in all platforms (Windows XP, Solaris-11)
b) This bug is not particular to old or new plugin
c) This bug is not specific to any browser.


Steps to produce the bug :
1) Install 6u10-b12 PIT
2) Open Java Control Panel
3) Go to the Advanced tab and select "Show Console"
4) Launch any applet (say http://java.sun.com/products/plugin/1.5.0/demos/plugin/applets/SimpleGraph/example1.html) in any browser
5) Java Console will come up, try to close it by clicking the close button or the close icon in the top right corner of the window.

If the Java colsole does not get closed, and throws the following error (while each click action), this bug is reproduced. 

[ Also see the attachment ]

Caused by: java.lang.ClassCastException: com.sun.deploy.services.WPlatformService cannot be cast to sun.plugin.services.BrowserService
	at sun.plugin2.main.client.Plugin2ConsoleController.isIconifiedOnClose(Unknown Source)
	at com.sun.deploy.util.ConsoleWindow.showConsole(Unknown Source)
	at sun.plugin.JavaRunTime$1.run(Unknown Source)
	at java.awt.event.InvocationEvent.dispatch(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)
Also see similar bug : 6659532