Proceedings the Third IEEE Workshop on Internet Applications. WIAPP 2003
DOI: 10.1109/wiapp.2003.1210298
|View full text |Cite
|
Sign up to set email alerts
|

Automatic failure-path inference: a generic introspection technique for Internet applications

Abstract: Automatic Failure-Path Inference (AFPI) is an application-generic, automatic technique for dynamically discovering the failure dependency graphs of componentized Internet applications. AFPI's first phase is invasive, and relies on controlled fault injection to determine failure propagation; this phase requires no a priori knowledge of the application and takes on the order of hours to run. Once the system is deployed in production, the second, non-invasive phase of AFPI passively monitors the system, and updat… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
54
0
1

Publication Types

Select...
5
4
1

Relationship

0
10

Authors

Journals

citations
Cited by 48 publications
(55 citation statements)
references
References 13 publications
(23 reference statements)
0
54
0
1
Order By: Relevance
“…The authors targeted Linux file system implementations at the source-code level and used block-level fault injection to confirm several categories of bugs. Tools for analyzing the propagation of Java exceptions have also been described by Candea et al [2003], Fu et al [2004], as well as Weimer and Necula [2008]. These tools use functional specifications that are known a priori.…”
Section: Related Workmentioning
confidence: 99%
“…The authors targeted Linux file system implementations at the source-code level and used block-level fault injection to confirm several categories of bugs. Tools for analyzing the propagation of Java exceptions have also been described by Candea et al [2003], Fu et al [2004], as well as Weimer and Necula [2008]. These tools use functional specifications that are known a priori.…”
Section: Related Workmentioning
confidence: 99%
“…The monitoring data we collect primarily includes the number of procedure invocations per minute of various Java modules (Java beans) in the application server while the Web service is in operation. We employ a failure-injection tool [5] to systematically inject failures into Rubis and JBoss. The types of failures injected in our experiments include Java exceptions, message drops, deadlocks, JNDI corruptions, data corruptions, memory leaks, and infinite loops.…”
Section: Methodsmentioning
confidence: 99%
“…Candea et al [7] used exception injection to capture the error-related dependencies between artifacts of an application. They inject checked exceptions as well as 6 runtime, unchecked exceptions.…”
Section: Related Workmentioning
confidence: 99%