Hi,
we have a service that subscribes to about a 1000 variables. It was working fine and suddenly we got warnings in in the event log and the datachange events started coming in with errors.
Below is the output from EasyUAClient.LogEntry
WARN 2016-10-10T10:10:41.817+01:00 OPCEvent OPC Event Source: OPCLabs-UAEngine Category: 0 Id:3012 Message: The OPC-UA subscription ID 3 publishing has stopped on the client session with connect sequence number 1 to endpoint URL "opc.tcp://localhost:49320" for approximate current duration of 75822 milliseconds. The current keep-alive count is 10, the current publishing interval is 7500 milliseconds, and the probationary period will be 5000 milliseconds. Further such errors on this session will not be logged.
WARN 2016-10-10T10:10:46.831+01:00 OPCEvent OPC Event Source: OPCLabs-UAEngine Category: 0 Id:3014 Message: The OPC-UA subscription ID 3 publishing has halted on the client session with connect sequence number 1 to endpoint URL "opc.tcp://localhost:49320" for approximate current duration of 80837 milliseconds. The current keep-alive count is 10, the current publishing interval is 7500 milliseconds, and the probationary period was 5000 milliseconds. Further such errors on this session will not be logged.
WARN 2016-10-10T10:10:46.850+01:00 OPCEvent OPC Event Source: OPCLabs-UAEngine Category: 0 Id:3201 Message: The status subscription for an OPC-UA session on endpoint URL "opc.tcp://localhost:49320" is in failure. Further such warnings on this session will not be logged.
The OPC-UA subscription ID 3 publishing has halted on the client session to endpoint URL "opc.tcp://localhost:49320" for approximate current duration of 80837 milliseconds. The current keep-alive count is 10, the current publishing interval is 7500 milliseconds, and the probationary period was 5000 milliseconds.
INFO 2016-10-10T12:48:30.614+01:00 OPCEvent OPC Event Source: OPCLabs-UAEngine Categoty: 0 Id:2071 Message: The keep-alive queue for the OPC-UA client session with connect sequence number 1 to endpoint URL "opc.tcp://localhost:49320" has overflown its limit of 100 entries. Further such warning on this session will not be logged.
WARN 2016-10-10T12:49:58.322+01:00 OPCEvent OPC Event Source: OPCLabs-UAEngine Category: 0 Id:2051 Message: The OPC-UA client session with connect sequence number 1 on endpoint URL "opc.tcp://localhost:49320" has encountered a publish error with code 0x80850000 for subscription ID 0 and sequence number 0. The error might be from the Publish or the Republish service. Further publish errors with this code on this session will not be logged.
Service result: BadRequestTimeout 'BadRequestTimeout'.
WARN 2016-10-10T12:49:58.324+01:00 OPCEvent OPC Event Source: OPCLabs-UAEngine Category: 0 Id:2051 Message: The OPC-UA client session with connect sequence number 1 on endpoint URL "opc.tcp://localhost:49320" has encountered a publish error with code 0x80250000 for subscription ID 0 and sequence number 0. The error might be from the Publish or the Republish service. Further publish errors with this code on this session will not be logged.
Service result: BadSessionIdInvalid 'BadSessionIdInvalid'.
When processing the data change events we started getting such errors for all of the variables:
WARN 2016-10-10T12:50:10.375+01:00 OPCEvent OPC Event Source: OPCLabs-UAEngine Category: 0 Id:3003 Message: Failed to remove subscription on the OPC-UA client session with connect sequence number 1 to endpoint URL "opc.tcp://localhost:49320". This error is generally ignored. Further such warnings on this session will not be logged. BadRequestTimeout
The server that the service was reading from was on the same machine.
There were other services that connected to that server and had no issues.
When I tried to reset the service it got stuck on unsubscribing and I had to kill the process.
The service was working fine for more than 2 weeks then after it was restarted it worked for about a day and then we got the above errors.
We are using the Nuget package and the version of the DLLs was 5.40.315.1
Do You have any ideas what can be the cause of such strange behavior ?
Regards,
Michal Waclawski
