Fix connection state recovery #5348
Closed
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.
The kind of change this PR does introduce
Current behavior
So far, all packets are being eliminated according to the time of their issuance, omitting completely the time of disconnection of the client. For example:
Customer A receives a packet broadcast at 10:00 AM and disconnects at 10:05 AM. However, the system deletes the packet based only on the broadcast time, without considering that the client was disconnected after 10:05 AM, thus causing the revision timeout that is executed every minute to delete the packet before disconnection and to always fail the recovery.
New behavior
All packages that are not required by any session are now removed to ensure that only the required packages are kept and not removed prematurely.
Other information (e.g. related issues)
#5282