JDK-7173640 : REGRESSION: Pogo 'Risk" grame can not load with 7u6
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version:
    5.0u51,6u31,6u34,6u51,7u6,7u10,7u25,8 5.0u51,6u31,6u34,6u51,7u6,7u10,7u25,8
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS:
    os_x,windows_xp,windows_7,windows_2012,windows_8 os_x,windows_xp,windows_7,windows_2012,windows_8
  • CPU: x86
  • Submitted: 2012-06-01
  • Updated: 2015-09-10
  • Resolved: 2012-06-06
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.
7u6Fixed 8 b42Fixed
Related Reports
Duplicate :  
Relates :  
J2SE Version (please include all output from java -version flag):
java version "1.7.0_06-ea"
Java(TM) SE Runtime Environment (build 1.7.0_06-ea-b12)

Does this problem occur on J2SE 6ux or 7ux?  Yes / No (pick one)
Yes, this issue happened on previous version
but works fine with 6u31

Operating System Configuration Information (be specific):
Microsoft Window XP Professional service pack 2
Microsoft Window 7 Ultimate service pack 1

Hardware Configuration Information (be specific):
System Manufacturer: Dell Inc.
       System Model: OptiPlex 380                 
               BIOS: Phoenix ROM BIOS PLUS Version 1.10 A03
          Processor: Intel(R) Core(TM)2 Duo CPU     E7500  @ 2.93GHz (2 CPUs)
             Memory: 2012MB RAM
          Page File: 1377MB used, 2527MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.2600.5512 32bit Unicode

Bug Description:
Game "Risk" can't be load by 'Play Now' button on Pogo site

Steps to Reproduce (be specific):
1. Go to www.pogo.com/games/risk
2. Click on startgame button
3. Observe the game alway call cripes and get lost connect issue.

Chrome configure has been part of test coverage. What applet(s) did Pogo have the issue with?

How about testing on Chrome Browser? Pogo had reported some games hangs, and Java crashes, but browser itself does not crash.

1)We used latest jre8b88 with Mac OS 10.8.2/x64/FF20/set2u config,The pogo games are passed 2)We used latest jre8b88 winvista-sp2/x86/IE9/set1u config ,The pogo games are passed 3)We used latest jre7u25b10 with solaris11/x86/FF19/set1u config,The pogo games are passed 4)We used latest jre7u25b10 withwin8/x86/IE10/set3u config,The pogo games are passed except one pogo case excluded(set3/pogo_HighStakesPool.html).. 5)We used latest jre7u25b10 with Mac OS 10.7.5/x64/FF20/set2uconfig ,The pogo games are passed

EVALUATION to allow 7u6 to load the risk applet, pogo needs to either increase heap size to workaround; or make their applet do not depend on re-using the same JVM. Please note that tuning the heap size is just a workaround. Solution is to stop relying on reuse of the same JVM for multiple applets. We can not guarantee it will not start failing again if they will stick to existing approach on relying on reuse of the same JVM for multiple applets.

EVALUATION problem: pogo risk game applet fail to load with 7u6 builds. we suspect it because we launch new jvm to run applet for the following cases, and their applets depend on all applets running in same jvm. 1. PluginMain.java, StartAppletListener appletSSVValidation, we have this code: if (selectedVersion.equals(runningVersion)) { with beta builds, for example, we compare between 1.8.0 and 1.8.0-ea, so we try to fire un-necessary jvm relaunch because of this. 2. JVMHealthData.java, isHealthy, when we make sure available heap size is okay: getAvailableHeapSize(): 25886008 HEALTHY_AVAILABLE_HEAP_SIZE: 33554432 then we try to kill the unhealthy jvm and relaunch: Relaunch due to unhealthy JVM: { healthy: false, ageSeconds: 34, availableHeapKB: 14799, appletThreads: 21 } fix: For 1, we ignore anything after '-' in the java.version value. For 2 - we think it's better to ask pogo to increase their max heap setting to 256 instead (from 128 now).