Publishing has halted on the client session - by: sjscheider

In my EasyUaClient.DataChangeNotification event handler, one of the first things I do is check if e.Exception is null. Since adding this code, I've noticed the following exception being reported:



Typically I see this error message in the log twice for a given node, with 0 to 5 milliseconds of one another.

How should I handle this exception in code? It does not appear to effect the functionality of the subscriptions. Are there setting in OPC Labs that I need to tweek? Any other recommendation?

The current test code is connected to 12 devices with subscriptions to 3 different node on each device. (One node at 500 milliseconds and two devices at 2000 milliseconds.) Over the course of about 8 hours and 15 minutes, there were 143 instance of the above exception.

I'm also seeing 126 instances of this exception over the same period of time with the DataChangeNotification event handler:

I also have a ServerConditionChanged event handler that fired 816 times during this period for either disconnecting or disconnected events. Example:

I'm still digging into the logs but it appear that these events are occurring across all of the devices.

I updated to the latest build yesterday and I'm still getting this issue. (version: 5.54.1151)