Details
-
Type: Bug
-
Status: Closed
-
Priority: Critical
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha2
-
Fix Version/s: 2.0-Alpha3, 2.0.0
-
Component/s: Sample Apps
-
Labels:None
-
Environment:Server: Tomcat 6
Browsers: IE6,7,8, FF3.5, Safari 4, Chrome 3, Opera 10 (Each has 2 tabs opened)
Description
When QA performing browser memory test on Tomcat 6 using multiple browsers described above, found in IE browsers (IE8,7,6), Safari 4 and Chrome 3, the clock stopped ticking after the test was started for about 10 minutes. A page reload would bring the clocks back to tick.
This issue does not happen to FF3.5 and Opera 10.
No exception/error showing in the server log files and server console.
This issue does not happen to FF3.5 and Opera 10.
No exception/error showing in the server log files and server console.
Issue Links
- depends on
-
PUSH-23 Auction updates stop after a variable period of time
- Closed
Testing with IE 6 under Wine and two tabs showed no connections to the server at the point of failure. Possibly the jsf.js queue has determined that the queue is full.