You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The method ProcessPublishResponse of the client session (Opc.Ua.Client.Session) probably generates false warning messages Sequence number={0} was not received in the available sequence numbers. The code that checks for the sequence numbers does not take into account the subscription id. If there is more than one subscription in the session then this code mixes up the sequence numbers from different sessions and issues the above mentioned message.
The code responsible:
foreach(var acknowledgement in acknowledgementsToSend){if(!availableSequenceNumbers.Contains(acknowledgement.SequenceNumber)){
Utils.Trace("Sequence number={0} was not received in the available sequence numbers.", acknowledgement.SequenceNumber);}}
The method
ProcessPublishResponse
of the client session (Opc.Ua.Client.Session
) probably generates false warning messages Sequence number={0} was not received in the available sequence numbers. The code that checks for the sequence numbers does not take into account the subscription id. If there is more than one subscription in the session then this code mixes up the sequence numbers from different sessions and issues the above mentioned message.The code responsible:
Suggested fix:
Can anybody confirm?
This is follow-up to the forum thread.
The text was updated successfully, but these errors were encountered: