Dear Support:
The following is the dilemma I encountered. I have no idea or clue for a long time. There is really no other way. I would like to ask for some advice.
Abnormal scenario description:
1 client.exe: windows server2019+ C# .Core7.0 + OpcLabs.EasyOpc.dll, OpcLabs.EasyOpcUA.dll ... ver: 5.80.255.2
2 A client.exe uses EasyUaClient to connect and subscribe to more than 80 different Opc Server devices
3 Abnormality: After working normally for a period of time, such as: a week later, a certain device cannot receive any subscribed data, and there is no task tracking log or disconnection retry log
4 EasyUaClient opens abnormal output and global tracking log output, but cannot find the log of the abnormal device,
5 When the abnormality occurs, the target device can be subscribed to and communicated with normally through third-party tool software (OpcUA)
6 Through the interface function of the software, the client is forced to notify the internal part. After canceling the subscription of the target device IP, the re-subscription can subscribe to the collected signal normally
The following are the relevant preparations I have made
1 The client.exe performs thread monitoring and log output every 20 seconds to understand the number of internal threads, TaskPool.Count, etc., and no abnormality is found
2 Memory usage is low, CPU load is low, no abnormality is observed
3 Other devices subscribe and collect normally
The situation described above has occurred several times in several of my projects. Because it involves the production environment, this abnormality must be resolved. Do you have any good suggestions and ideas to help me solve it?
Looking forward to your attention and reply
Simon.Yu
2025.7.7 15:59
www.vskysoft.com