Activity log for bug #1335757
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2014-06-30 07:51:22 | Nischal Sheth | bug | added bug | ||
| 2014-06-30 07:51:58 | Nischal Sheth | description | Couple of issues in XmppConnection cleanup have been identified when trying to stabilize bgp_stress_test and bgp_xmpp_deferq_test: - LifetimeManager is not used correctly - the actor is enqueued to the manager directly from the ManagedDelete method instead of invoking the LifetimeActor Delete method. Given the right sequence of events this causes problems when the connection is deleted from both above (due to test TearDown) and below (due to the mock agent bringing down the session) - XmppConnections that are rejected during dequeue (because there's already a connection from the same IP) are not tracked properly. This causes problems such as deletion of a different incarnation of the connection (i.e. same IP but not the same data structure). Both the above result in assertion failures in the LifetimeActor destructor. | Couple of issues in XmppConnection cleanup have been identified when trying to stabilize bgp_stress_test and bgp_xmpp_deferq_test: - LifetimeManager is not used correctly - actor is enqueued to the manager directly from the ManagedDelete method instead of invoking the LifetimeActor Delete method. Given the right sequence of events this causes problems when the connection is deleted from both above (due to test TearDown) and below (due to the mock agent bringing down the session) - XmppConnections that are rejected during dequeue (because there's already a connection from the same IP) are not tracked properly. This causes problems such as deletion of a different incarnation of the connection (i.e. same IP but not the same data structure). Both the above result in assertion failures in the LifetimeActor destructor. | |
| 2014-06-30 21:47:37 | Nischal Sheth | juniperopenstack: status | New | In Progress | |
| 2014-07-27 06:53:37 | Nischal Sheth | juniperopenstack: status | In Progress | Fix Committed | |
| 2014-09-22 17:07:35 | Nischal Sheth | description | Couple of issues in XmppConnection cleanup have been identified when trying to stabilize bgp_stress_test and bgp_xmpp_deferq_test: - LifetimeManager is not used correctly - actor is enqueued to the manager directly from the ManagedDelete method instead of invoking the LifetimeActor Delete method. Given the right sequence of events this causes problems when the connection is deleted from both above (due to test TearDown) and below (due to the mock agent bringing down the session) - XmppConnections that are rejected during dequeue (because there's already a connection from the same IP) are not tracked properly. This causes problems such as deletion of a different incarnation of the connection (i.e. same IP but not the same data structure). Both the above result in assertion failures in the LifetimeActor destructor. | Couple of issues in XmppConnection cleanup have been identified when trying to stabilize bgp_stress_test and bgp_xmpp_deferq_test: - LifetimeManager is not used correctly - actor is enqueued to the manager directly from the ManagedDelete method instead of invoking the LifetimeActor Delete method. Given the right sequence of events this causes problems when the connection is deleted from both above (due to test TearDown) and below (due to the mock agent bringing down the session) - XmppConnections that are rejected during dequeue (because there's already a connection from the same IP) are not tracked properly. This causes problems such as deletion of a different incarnation of the connection (i.e. same IP but not the same data structure). Both the above result in assertion failures in the LifetimeActor destructor. | |
| 2014-09-22 17:08:03 | Nischal Sheth | juniperopenstack: status | Fix Committed | Fix Released | |
| 2015-04-28 21:04:48 | Nischal Sheth | information type | Proprietary | Public |
