Origin of Bad_SequenceNumberUnknown log outputs
Posted: 21 Jul 2022, 14:39
Dear all,
working with the Java OPC UA SDK, I sometimes see log messages like the ones below while running an OPC UA client with monitored items pointing to another OPC UA server. I would like to understand more about why we are seeing these and whether we should do something about them.
[INFO ] 2022-07-21 15:32:03.230 [OPC-UA-Stack-Blocking-Work-Executor-5] Subscription - Acknowledge on Subscription 1: 154 - Bad_SequenceNumberUnknown
[INFO ] 2022-07-21 15:32:03.231 [OPC-UA-Stack-Blocking-Work-Executor-3] Subscription - Acknowledge on Subscription 1: 154 - Bad_SequenceNumberUnknown
[INFO ] 2022-07-21 15:32:03.231 [OPC-UA-Stack-Blocking-Work-Executor-3] Subscription - Acknowledge on Subscription 1: 155 - Bad_SequenceNumberUnknown
I would appreciate any assistance you might be able to give to identify the root cause.
Thanks, Gerald
working with the Java OPC UA SDK, I sometimes see log messages like the ones below while running an OPC UA client with monitored items pointing to another OPC UA server. I would like to understand more about why we are seeing these and whether we should do something about them.
[INFO ] 2022-07-21 15:32:03.230 [OPC-UA-Stack-Blocking-Work-Executor-5] Subscription - Acknowledge on Subscription 1: 154 - Bad_SequenceNumberUnknown
[INFO ] 2022-07-21 15:32:03.231 [OPC-UA-Stack-Blocking-Work-Executor-3] Subscription - Acknowledge on Subscription 1: 154 - Bad_SequenceNumberUnknown
[INFO ] 2022-07-21 15:32:03.231 [OPC-UA-Stack-Blocking-Work-Executor-3] Subscription - Acknowledge on Subscription 1: 155 - Bad_SequenceNumberUnknown
I would appreciate any assistance you might be able to give to identify the root cause.
Thanks, Gerald