Similar to issue 957 in the UA-.NETStandard repo, I am experiencing event ordering issues with a Subscription object that contains multiple MonitoredItem objects.
Occasionally I will get event notifications through the MonitoredItem's Notification callback out of order from how the UA Server is sending them. This causes a bunch of upstream problems as the rest of the system was assuming these events were coming in ordered.
I know this is an old non-maintained repo, however I figure asking whether anyone else has this problem on the legacy clients can't hurt. If you have and have a work around, I would love you hear it.
For reference my Subscription object has a KeepAliveCount of 10, a LifetimeCount of 100 and a MaxNotificationsPerPublish of 100. My MonitoredItem objects have a SamplingInterval of 0, a QueueSize of 1000 and is set to DiscardOldest values.
Similar to issue 957 in the UA-.NETStandard repo, I am experiencing event ordering issues with a
Subscriptionobject that contains multipleMonitoredItemobjects.Occasionally I will get event notifications through the
MonitoredItem'sNotificationcallback out of order from how the UA Server is sending them. This causes a bunch of upstream problems as the rest of the system was assuming these events were coming in ordered.I know this is an old non-maintained repo, however I figure asking whether anyone else has this problem on the legacy clients can't hurt. If you have and have a work around, I would love you hear it.
For reference my
Subscriptionobject has aKeepAliveCountof 10, aLifetimeCountof 100 and aMaxNotificationsPerPublishof 100. MyMonitoredItemobjects have aSamplingIntervalof 0, aQueueSizeof 1000 and is set toDiscardOldestvalues.