Hi Dojo,
After an upgrade from 10.5.4 to 1.5.9, when the agents came back online, several notice alarms for different agents reported an unexpected exception.
Although these notices don’t appear to affect the normal operation of the DMS, it’s unclear what their actual meaning or potential impact on the system might be.
Has anyone encountered this before and can share insight on what it means and whether it could have any impact on the system?
Hi,
This is a new verification when subscribing on an agent that all events are properly handled and there are no race conditions.
This might make the connections be in an inconsistent state.
Best to recreate the connections by connecting to the agent that threw the alarm and do DropSLNetConnections: 
Note: the alarms won't clear automatically, so best clear them manually and see if check if they reappear.
Hi Catarina,
haven't experienced this myself (I'm on the main release path) but from the looks of the stack it seems that DM is not able to process events within the expected time window.
The stack trace points to Skyline.DataMiner.Net.Notifications.NotificationManager.WaitUntilAllCurrentItemsHandled.
If some tasks are blocking the notification queue from clearing, this might lead to timeouts in WaitUntilAllCurrentItemsHandled - if the issue persists after a restart, you may want to increase the logging level to possibly fetch and isolate the cause of these many parameter changes.
Subscribing to get more insights from the community.
HTH
Hi Catarina – Was there a change in the DMA connection as part of the upgrade?