Who is to blame? – Runtime verification of distributed objects with active monitors

Wolfgang Ahrendt, Ludovic Henrio, Wytse Oortwijn

    Research output: Contribution to journalConference articleAcademicpeer-review

    51 Downloads (Pure)


    Since distributed software systems are ubiquitous, their correct functioning is crucially important. Static verification is possible in principle, but requires high expertise and effort which is not feasible in many eco-systems. Runtime verification can serve as a lean alternative, where monitoring mechanisms are automatically generated from property specifications, to check compliance at runtime. This paper contributes a practical solution for powerful and flexible runtime verification of distributed, object-oriented applications, via a combination of the runtime verification tool LARVA and the active object framework PROACTIVE. Even if LARVA supports in itself only the generation of local, sequential monitors, we empower LARVA for distributed monitoring by connecting monitors with active objects, turning them into active, communicating monitors. We discuss how this allows for a variety of monitoring architectures. Further, we show how property specifications, and thereby the generated monitors, provide a model that splits the blame between the local object and its environment. While LARVA itself focuses on monitoring of control-oriented properties, we use the LARVA front-end STARVOORS to also capture data-oriented (pre/post) properties in the distributed monitoring. We demonstrate this approach to distributed runtime verification with a case study, a distributed key/value store.

    Original languageEnglish
    Pages (from-to)32-46
    Number of pages15
    JournalElectronic Proceedings in Theoretical Computer Science, EPTCS
    Publication statusPublished - 27 Aug 2019
    Event2nd Workshop on Verification of Objects at RunTime EXecution, VORTEX 2018 - Amsterdam, Netherlands
    Duration: 17 Jul 201817 Jul 2018
    Conference number: 2


    Dive into the research topics of 'Who is to blame? – Runtime verification of distributed objects with active monitors'. Together they form a unique fingerprint.

    Cite this