JDK-6627386 : JavaScript errors with gamehouse.com applets
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: generic
  • CPU: generic
  • Submitted: 2007-11-08
  • Updated: 2010-05-05
  • Resolved: 2008-01-05
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
6u10Resolved
Related Reports
Relates :  
JDK-6618920 - Plugin2 : Add classloader caching support to new Plug-in
Relates :  
JDK-6616692 - Two Java consoles exist when refresh the game applets
Relates :  
JDK-6592751 - EmbeddedFrame disposal is fragile and breaks clean AppContext termination
Description
The applets at www.gamehouse.com are reporting JavaScript errors apparently because multiple applets hosted on the same page are not properly seeing each other. At the present time it is unclear whether this is a bug in the new Java Plug-In or a bug in the gamehouse.com games.

To reproduce, enable the display of all JavaScript errors in Internet Explorer, enable the Java Console, and run for example the Caribbean Stud poker game from the Online Casino games.

With the recent fix for 6618920 in place, the expectation is that multiple applets on the same page should see each other as expected. This has been verified for example with games from pogo.com.

Applying the proposed fix for 6592751 may make it easier to reproduce the problem, since the JVM won't keep getting killed if some of the applets fail to terminate 100% cleanly.

It would be good if we could get in touch with www.gamehouse.com and have them test with the new Java Plug-In to get a better idea if this is a problem on our side or theirs.
Comments
EVALUATION The JavaScript errors appear to be errors in the gamehouse.com applets and web pages. The applet attempts to call into JavaScript upon loading which provokes the following exception: netscape.javascript.JSException: Failure to evaluate javascript:gameloaded('stud') at sun.plugin2.main.client.MessagePassingJSObject.newJSException(MessagePassingJSObject.java:223) at sun.plugin2.main.client.MessagePassingJSObject.waitForReply(MessagePassingJSObject.java:137) at sun.plugin2.main.client.MessagePassingJSObject.eval(MessagePassingJSObject.java:76) at Boomerang.client.BoomUser.callJavascript(Boomerang/client/BoomUser) at Boomerang.client.BoomUser.runCommand(Boomerang/client/BoomUser) at sprite.GameCanvas.start(sprite/GameCanvas) at gamehouse.SuperApplet.run(gamehouse/SuperApplet) at java.lang.Thread.run(Thread.java:619) Examining the source of the surrounding web page shows that there is no "gameloaded" JavaScript function defined, which explains the reason for the JSException. The JavaScript exceptions on the browser side don't appear to be Java-related; it doesn't look like any JavaScript -> Java calls are made. Closing as "Not a Defect".
05-01-2008