Back to bug 1316282
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Greg Blomquist | 2016-03-10 14:30:28 UTC | Priority | unspecified | high |
| Assignee | gblomqui | agrare | ||
| Greg Blomquist | 2016-03-10 14:59:20 UTC | CC | gblomqui, jdeubel | |
| Flags | needinfo?(jdeubel) | |||
| Jared Deubel | 2016-03-10 15:45:07 UTC | Flags | needinfo?(jdeubel) | |
| Nandini Chandra | 2016-03-11 19:14:30 UTC | CC | nachandr | |
| Whiteboard | event | |||
| Adam Grare | 2016-03-11 19:52:03 UTC | Status | NEW | ASSIGNED |
| Adam Grare | 2016-03-24 18:47:07 UTC | Status | ASSIGNED | POST |
| John Prause | 2016-03-28 14:59:00 UTC | Status | POST | MODIFIED |
| CC | jprause | |||
| Oleg Barenboim | 2016-03-29 13:13:02 UTC | Summary | Eventing stops working shortly after an appliance reboot (20-30 minute) | Events from vSphere stop working shortly after an appliance reboot (20-30 minute) |
| John Prause | 2016-03-29 14:29:19 UTC | Blocks | 1322002 | |
| John Prause | 2016-03-29 14:29:51 UTC | Keywords | ZStream | |
| John Prause | 2016-03-29 14:33:22 UTC | Blocks | 1322004 | |
| Satoe Imaishi | 2016-04-13 21:37:34 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | 5.6.0.1 | |||
| Dave Johnson | 2016-04-15 21:45:23 UTC | QA Contact | dajohnso | nachandr |
| Nandini Chandra | 2016-04-27 21:21:42 UTC | CC | agrare | |
| Flags | needinfo?(agrare) | |||
| Adam Grare | 2016-04-28 13:21:28 UTC | Flags | needinfo?(agrare) | |
| Nandini Chandra | 2016-04-28 22:18:09 UTC | Flags | needinfo?(jdeubel) | |
| Nandini Chandra | 2016-04-29 03:58:14 UTC | Status | ON_QA | VERIFIED |
| Marianne Feifer | 2016-05-02 19:56:44 UTC | CC | mfeifer | |
| Doc Text | Cause: Using HTTP timeout with WaitForUpdates was causing calls to hang eventually. Consequence: Events from vSphere stop working shortly after an appliance reboot (20-30 minute) ( Fix: In vSphere 4.1 VMware added a new method WaitForUpdatesEx to address the issue of WaitForUpdates blocking for a long time. Using the maxWait option to WaitForUpdatesEx we can control how long to block in WaitForUpdatesEx without resorting to timing out the connection. Result: |
|||
| Jared Deubel | 2016-05-26 15:24:54 UTC | Flags | needinfo?(jdeubel) | |
| Dayle Parker | 2016-06-27 04:10:47 UTC | Doc Text | Cause: Using HTTP timeout with WaitForUpdates was causing calls to hang eventually. Consequence: Events from vSphere stop working shortly after an appliance reboot (20-30 minute) ( Fix: In vSphere 4.1 VMware added a new method WaitForUpdatesEx to address the issue of WaitForUpdates blocking for a long time. Using the maxWait option to WaitForUpdatesEx we can control how long to block in WaitForUpdatesEx without resorting to timing out the connection. Result: | Previously, using HTTP timeout with WaitForUpdates caused calls to VMware vSphere to hang. Consequently, vSphere events stopped working 20-30 minutes after an appliance reboot. VMware vSphere 4.1 added the WaitForUpdatesEx method to address the issue of WaitForUpdates blocking processes for a long time. This CloudForms release contains WaitForUpdatesEx, which can be used with the maxWait property to configure blocking limits for WaitForUpdatesEx without needing to time out the connection. |
| Dayle Parker | 2016-06-27 05:28:22 UTC | Doc Text | Previously, using HTTP timeout with WaitForUpdates caused calls to VMware vSphere to hang. Consequently, vSphere events stopped working 20-30 minutes after an appliance reboot. VMware vSphere 4.1 added the WaitForUpdatesEx method to address the issue of WaitForUpdates blocking processes for a long time. This CloudForms release contains WaitForUpdatesEx, which can be used with the maxWait property to configure blocking limits for WaitForUpdatesEx without needing to time out the connection. | Previously, using HTTP timeout with the WaitForUpdates method caused calls to VMware vSphere to hang. Consequently, vSphere events stopped working 20-30 minutes after an appliance reboot. VMware vSphere 4.1 added the WaitForUpdatesEx method to address the issue of WaitForUpdates blocking processes for a long time. This CloudForms release contains WaitForUpdatesEx, which can be used with the maxWait property to configure blocking limits for WaitForUpdatesEx without needing to time out the connection. |
| errata-xmlrpc | 2016-06-29 07:17:59 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-06-29 15:41:10 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-06-29 11:41:10 UTC |
Back to bug 1316282