Notification Server crashes if Peripheral timestamp received out of order
| Issue date | October 10, 2014 | |
| Observed behavior | Notification Server crashes and will not automatically restart if the time stamp from when the Peripheral Monitorservice is restarted is earlier than the system time when the Peripheral Monitor was last started. | |
| Products and versions affected | Virtual Hold Callback version 8.0.5 | |
| Components affected | System Management API and User Interface | |
| Applications affected | System Management | |
| Severity | Critical | |
| Root cause | A time stamp comparison in the Notification Server does not properly handle the case when Peripheral Instanceupdates are received out of order. This may occur if the system time is manually set to an earlier time, and the VHTPeripheral Monitor Service is restarted. | |
| Resolution | Upgrade to one of the following versions located in the Virtual Hold Download Center (https://virtualhold.flexnetoperations.com):
| |
| Expected availability | Virtual Hold version 8.0.6 HF3 ( available late October 2014) | |
| Workarounds | Follow the steps in the "Correcting Datastore Clustering Problems" Appendix of the Virtual Hold Deployment Guide. | |
| Defects related to this issue | 80320012 | Notification Server crashes if peripheral time stamp received out of order |
