Tranquility: A Low Disruptive Alternative to Quiescence for Ensuring Safe Dynamic Updates

This paper revisits a problem that was identified by Kramer and Magee: placing a system in a consistent state before and after runtime changes. We show that their notion of quiescence as a necessary and sufficient condition for safe runtime changes is too strict and results in a significant disrupti...

Full description

Saved in:
Bibliographic Details
Published inIEEE transactions on software engineering Vol. 33; no. 12; pp. 856 - 868
Main Authors Vandewoude, Y., Ebraert, P., Berbers, Y., D'Hondt, T.
Format Journal Article
LanguageEnglish
Published New York IEEE 01.12.2007
IEEE Computer Society
Subjects
Online AccessGet full text

Cover

Loading…
More Information
Summary:This paper revisits a problem that was identified by Kramer and Magee: placing a system in a consistent state before and after runtime changes. We show that their notion of quiescence as a necessary and sufficient condition for safe runtime changes is too strict and results in a significant disruption in the application being updated. In this paper, we introduce a weaker condition: tranquillity. We show that tranquillity is easier to obtain and less disruptive for the running application but still a sufficient condition to ensure application consistency. We present an implementation of our approach on a component middleware platform and experimentally verify the validity and practical applicability of our approach using data retrieved from a case study.
Bibliography:ObjectType-Article-1
SourceType-Scholarly Journals-1
ObjectType-Feature-2
content type line 23
ObjectType-Article-2
ObjectType-Feature-1
ISSN:0098-5589
1939-3520
DOI:10.1109/TSE.2007.70733