Fixes #1276 timestamp check in server keep-alive monitor (#1277)

* Fix timestamp check in server keep-alive monitor

* Retain the original client statistics property name
- add comments to clarify meaning
- add separate public "received" timestamp property

* fix comment
This commit is contained in:
logicaloud
2021-10-30 10:12:57 +02:00
committed by GitHub
parent d7e1c89d62
commit 1e68c2e815
3 changed files with 45 additions and 3 deletions
@@ -647,6 +647,39 @@ namespace MQTTnet.Tests.Client
}
}
[TestMethod]
public async Task Publish_QoS_0_Over_Period_Exceeding_KeepAlive()
{
using (var testEnvironment = new TestEnvironment(TestContext))
{
const int KeepAlivePeriodSecs = 3;
await testEnvironment.StartServer();
var options = new MqttClientOptionsBuilder().WithKeepAlivePeriod(TimeSpan.FromSeconds(KeepAlivePeriodSecs));
var client = await testEnvironment.ConnectClient(options);
var message = new MqttApplicationMessageBuilder().WithTopic("a").Build();
try
{
// Publish messages over a time period exceeding the keep alive period.
// This should not cause an exception because of, i.e. "Client disconnected".
for (var count = 0; count < KeepAlivePeriodSecs * 3; ++count)
{
// Send Publish requests well before the keep alive period expires
await client.PublishAsync(message);
await Task.Delay(1000);
}
}
catch (Exception ex)
{
Assert.Fail(ex.Message);
}
}
}
[TestMethod]
public async Task Subscribe_In_Callback_Events()
{