View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000902710000-004: ServicesSpecpublic2023-06-23 10:162023-06-23 14:13
ReporterMatthias Damm Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.02 
Fixed in Version1.05.03 RC1 
Summary0009027: Clean-up strategy for retransmission queue in Server
Description

We identified a gap in the specification for the case that acknowledgements of NotificationMessages from Clients get lost because the related Publish request was lost due to connection problems.

This leads to dead NotificationMessages in the retransmission queue of the Server. If the queu does not overflow, the old NotificationMessages stay in memory for ever.

In long running Subscriptions this causes a growing memory consuption that is not a memory leak but can sum up to overall memory issues.

Currently the server would not be allowed to delete very old NotificationMessages from the queue.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Matthias Damm

2023-06-23 10:22

developer   ~0019663

Current text in the spec implies already that the Client acknowledges all older Notifications with the Publish request

5.13 Subscription Service Set
5.13.1 Subscription model
5.13.1.1 Description
Publish requests allow the Client to acknowledge all Notifications up to a specific sequence number and to acknowledge the sequence number of the last NotificationMessage received.

Matthias Damm

2023-06-23 14:00

developer   ~0019666

5.13 Subscription Service Set
5.13.1 Subscription model
5.13.1.1 Description

Added:
If the retransmission queue contains outdated sequence numbers related to the sequence number acknowledged by the Client, the Server may delete these older NotificationMessage from the retransmission queue. The outdated sequence numbers are calculated with the following formular.
outdated < acknowledged sequence number – (2 x max retransmission queue size)

Jim Luth

2023-06-23 14:13

administrator   ~0019667

Agreed to changes edited in Virtual F2F.

Issue History

Date Modified Username Field Change
2023-06-23 10:16 Matthias Damm New Issue
2023-06-23 10:16 Matthias Damm Status new => assigned
2023-06-23 10:16 Matthias Damm Assigned To => Matthias Damm
2023-06-23 10:22 Matthias Damm Note Added: 0019663
2023-06-23 14:00 Matthias Damm Status assigned => resolved
2023-06-23 14:00 Matthias Damm Resolution open => fixed
2023-06-23 14:00 Matthias Damm Fixed in Version => 1.05.03 RC1
2023-06-23 14:00 Matthias Damm Note Added: 0019666
2023-06-23 14:13 Jim Luth Status resolved => closed
2023-06-23 14:13 Jim Luth Note Added: 0019667