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
-
Activity
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Fix Version/s | 2.0.0 [ 10230 ] |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Assignee Priority | P2 | |
| Resolution | Fixed [ 1 ] |
| Salesforce Case | [] | |
| Fix Version/s | 2.0-Beta [ 10032 ] | |
| Fix Version/s | 2.0-Alpha2 [ 10214 ] | |
| Assignee Priority | P1 | P2 |
| Salesforce Case | [] | |
| Assignee Priority | P1 |
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Assignee Priority | P1 | |
| Resolution | Fixed [ 1 ] |
| Comment |
[ Using e.name and e.message, the exception appears to be: updateException Invalid argument So perhaps we are passing something strange to jsf.ajax.request. ] |
| Comment |
[ Still failing on IE browsers: Clocks tick for me on Firefox (perhaps this is what was fixed by clearing the cookies). However, with IE 6, I have verified that the notifications are being received and retrieveUpdate() is being called in the browser, but an exception is being thrown in this method: "failed to pick updates[object error]" (Looks like the exception doesn't have a proper toString()). Ted. ] |
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #20218 | Wed Jan 13 15:21:42 MST 2010 | mircea.toma | |
| Files Changed | ||||
MODIFY
/projects/bridge-support/src/main/javascript/cookie.js
|
| Salesforce Case | [] | |
| Assignee Priority | P2 | P1 |
| Assignee | Ted Goddard [ ted.goddard ] | Mircea Toma [ mircea.toma ] |
| Priority | Major [ 3 ] | Critical [ 2 ] |
| Salesforce Case | [] | |
| Fix Version/s | 2.0-Alpha2 [ 10214 ] |
| Salesforce Case | [] | |
| Assignee Priority | P2 | |
| Assignee | Ken Fyten [ ken.fyten ] | Ted Goddard [ ted.goddard ] |
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Ken Fyten [ ken.fyten ] |

Changes to remove the ThreadLocal and use request attributes have remedied the problem of staring push with multiple browsers instances running. However, push is still timing out after a variable amount of time which at this point does not look related to the type or version of browser.
Our current data indicates that push groups are being cleaned up too early and the cause may be related to the calculation of the lastAccess time in PushContext.Group class. Typically, each incoming request with valid push ids would touch the lastAccess time indicating the push group was still valid. However, there seems to be an issue which causes these requests to not update the lastAccess time. Continuing to investigate.