Unexpected client "SubscriptionId = 0" error trace in log files

Description

• A S2OPC-based client connects to a S2OPC-based server and creates a subscription (SubscriptionId=300).
• Before any MI are set in the subscription, the client sends 3 PublishRequest (Id=5, 6 and 7)
• When the client Add MI to the subscription, the server responds to the first PublishRequest with a valid PublishResponse (ReqId = 5 in Pcap) containing SubscriptionId=300
• The Client sends a new PublishRequest (I don't know if this matters)
• The server sends a PublishResponse for ReqId=6 and 7 with a bad SubscriptionId=0 (instead of 300)

Code version and environment identification

b2b6619

Relevant logs and/or screenshots

badSubscriptionId0.pcapng

Analysis

The issue is that it appears in the client log files and not the response content. SubscriptionId = 0 is expected because the PublishResponse is returned with Bad_Timeout due to publish request timeout hint provided, thus the PublishResponse is not associated to a subscription in this case.

Security impact

No impact.

Possible fixes

Avoid to display error log trace in this particular case