Details
Bug
Major
Description
When new tabs/windows are opened to same application the blocking connection can change the owning window. When this occurs the heartbeat of the window that used to own the blocking connection does not shutdown its heartbeat. As a result pings are send by all the windows that used to own the blocking connection at some point in time.
Activity
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #19249 | Mon Sep 14 13:18:31 MDT 2009 | mircea.toma | |
| Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/bridge/src/connection.async.js
|
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case | [] | |
| Fix Version/s | 1.8.2 [ 10190 ] | |
| Assignee | Mircea Toma [ mircea.toma ] |
| Salesforce Case | [] | |
| Description | When new tabs/windows are opened to same application the blocking connection can change the owning window. When this occurs the heartbeat of the window that used to own the blocking connection does not shutdown its heartbeat. As a result pings are send by all the windows that used to own at some point in the blocking connection. | When new tabs/windows are opened to same application the blocking connection can change the owning window. When this occurs the heartbeat of the window that used to own the blocking connection does not shutdown its heartbeat. As a result pings are send by all the windows that used to own the blocking connection at some point in time. |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 1.8.2-RC1 [ 10210 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Shutdown the heartbeat of the bridge instance when the server requests a shutdown of the blocking connection (marked by the X-Connection custom header).