Implemented server keep alive setting and usage in connect #883
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release notes
Added configuration setting so that the broker can specify a keep alive other then the one selected by clients.
What does this PR do?
Updates the configuration harness to expose a duration setting name
server_keep_alive
.Updated the connAck properties creation to include
server keep alive
if the broker configuration has selected it.Updates the connect processing to leverage the
server keep alive
selected keep alive instead of the client one.Why is it important/What is the impact to the user?
Checklist
Author's Checklist
How to test this PR locally
Related issues
Use cases