Still valid for 1.4.9.396

The test script has been updated, so that a PublishingInterval of 1000 ms is requested when creating the Subscription.
Note: The current implementation is using the "Default Subscription Publish Interval" setting of the CTT. To validate the correct behavior of the server for this test case, you can increase this setting to a suitable value.

Reviewed in CMP call. Agreed to changes and closed

Sorry, but changing the publishing interval did not really change anything.
Actually the same issue also affects the also Session / Session Change User / 002.js and 004.js,
those still use a 250 ms sampling interval, but they also fail sporadically, in a very similar way.

We think we have is a race condition between the revised publishing interval of the subscription (1000ms),
and the revised sampling interval of the monitored item (also 1000ms, but starts when the MI is created),
and the time when the publish request is sent, which is also done after 1000ms almost in sync with the publishing interval,
and the internal timer that increments the CurrentTime variable, also executed every 1000ms but asynchronously to the publishing.

This capture "mantis5652.pcapng" shows how the 002.js and 004.js fail.
The first publish request is a few milliseconds too early, and therefore
an keep alive is returned.
I think this failure would likely be fixed by changing these scripts to
use 1000 ms publishing interval like the 001.js does.

However this capture "mantis5652_fali1.pcapng" shows how 001.js fails,
NOTE: and both 002.js and 004.js are manually changed to use
var ChangeUserSubscription = new Subscription( 1000 );

I am not sure if the server is allowed to send a keepalive after the
subscription has publishing interval = 1000ms and maxKeepAlive = 3,
so if that is wrong, we have to fix that, otherwise you will need
to add a small extra delay here.

Adopted the changes (increase PublishingInterval to 1 second) of the initial solution to all other test scripts of this Conformance Unit.
Also set the FirstPublish parameter when sending Publish for the first time. This allows server to provide an empty KeepAlive after the first publishing interval has been elapsed if no sample is yet available.

Reviewed issue in call, agreed to changes and closed issue