Corrected Cancellation Source for KeepAlive Messages

[Erw1nT]

I found out that the issue found in #2108 likely comes due to the fact that the wrong duration is used for checking the keep alive interval.

In this test setup i connect to a public broker and use the approach described in #2108 to see if it is triggered within time.
https://github.com/Erw1nT/MqttKeepAlive/blob/master/Program.cs

Only when this line is added, the connection-changed/disconnected event is fired in time.

.WithTimeout(TimeSpan.FromSeconds(KeepAliveTimeInSeconds))

[chkr1011]

Please see my comment.

[Erw1nT]

@chkr1011 Thank you for reviewing and improving the PR.

[Erw1nT]

@chkr1011 We are currently using v4.3.6 in our application and rely on the ManagedMqttClient as of now.
Due to time/budget constraints it would be best for us, if this bugfix would be made available in a v4.3.8 so that we do not have to implement and test a re-connect logic that the ManagedClient offers. And also not handle all other breaking changes...
Is that possible?
Thanks in advance.

[chkr1011]

I will create a port for version 4 soon.

[Erw1nT]

@chkr1011 Have you had any time for the port yet. Would really appreciate it. (I can also see why it's not a high priority ;))

[chkr1011]

@Erw1nT High priority does not mean it will be done tomorrow. For a project which is maintained by people in their free time, it means it is only one of the first things which is done as soon as the developers have some free time to work on it ;-)

A new PR is here: #2144
Please test latest version 4.3.8 (as soon as available) from myget feed and let me know if it works properly.

[Erw1nT]

@chkr1011 It does work as expected now. Thank you for your support.