2016
DOI: 10.1007/978-3-319-33693-0_12
|View full text |Cite
|
Sign up to set email alerts
|

On Implementing a Monitor-Oriented Programming Framework for Actor Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
40
0

Year Published

2016
2016
2023
2023

Publication Types

Select...
6
1

Relationship

2
5

Authors

Journals

citations
Cited by 31 publications
(40 citation statements)
references
References 28 publications
0
40
0
Order By: Relevance
“…Initially, this work took advantage of Erlang's tracing mechanism to hook into Erlang's virtual machine to receive events as messages [23]. More recent work [18,19] employs an Aspect-Oriented Programming framework to inject instrumentation as in AspectJ. It should be noted that when monitoring Erlang programs there is an additional issue of distributed (asynchronous) computation to contend with.…”
Section: Instrumentation Techniquesmentioning
confidence: 99%
“…Initially, this work took advantage of Erlang's tracing mechanism to hook into Erlang's virtual machine to receive events as messages [23]. More recent work [18,19] employs an Aspect-Oriented Programming framework to inject instrumentation as in AspectJ. It should be noted that when monitoring Erlang programs there is an additional issue of distributed (asynchronous) computation to contend with.…”
Section: Instrumentation Techniquesmentioning
confidence: 99%
“…Recent work [15,4,8,28,16] studies the application of online RV to general specification properties describing the branching structure of the system under scrutiny. This is of particular relevance to concurrent (component) systems with multiple executions.…”
Section: Introductionmentioning
confidence: 99%
“…Even though several monitoring tools [14,23,15,20] exists for renowned languages such as Java, the only tools developed specifically for Erlang are detectEr [4,7] and adaptEr [9,8]. In this paper we therefore give an overview of these two runtime monitor tools.…”
Section: Monitormentioning
confidence: 99%
“…Adaptation actions are rectifying actions (such as restarting or terminating misbehaving actors) in order to mitigate the effects incurred by a detected violation. This extension led to the creation of a Runtime Adaptation tool called adaptEr [8,9]. In this property, the specifier presumes that the error (which may arise after a number of correct interactions) is caused by the interface actor i (as shown in Figure 2, where an inc request is erroneously forwarded to the decrementor actor k) -one may, for instance, have prior knowledge that actor i is a newly-installed, untested component.…”
Section: Runtime Adaptation With Adaptermentioning
confidence: 99%
See 1 more Smart Citation