Issue 10811: Default built-in ReaderDataLifecycle values (data-distribution-rtf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: Problem:
QoS settings of buildin Readers: according to section 2.1.5 builtin Readers should have its ReaderDataLifecycles delays set to infinite, meaning that builtin topics that are disposed and/or unregistered will never be removed from the system unless explicitly 'taken'. If an application never bothers to look at the builtin readers, they will never clean up resources and these readers will use up more and more memory if entities keep on joining and leaving the network. 

Solution:
We propose to give the builtin-readers a finite duration for both auto_purge variables (for example something like 5 minutes).

Resolution: 
Revised Text: 
Actions taken:
March 5, 2007: received issue
Discussion: 

End of Annotations:=====
s is issue # 10811	From: "Robert Poth" <Robert.Poth@prismtech.com>


Default built-in ReaderDataLifecycle values

Problem:
QoS settings of buildin Readers: according to section 2.1.5 builtin Readers should have its ReaderDataLifecycles delays set to infinite, meaning that builtin topics that are disposed and/or unregistered will never be removed from the system unless explicitly 'taken'. If an application never bothers to look at the builtin readers, they will never clean up resources and these readers will use up more and more memory if entities keep on joining and leaving the network. 

Solution:
We propose to give the builtin-readers a finite duration for both auto_purge variables (for example something like 5 minutes).