Fault-Tolerant BPEL Workflow Execution via Cloud-Aware Recovery Policies

Juhnke, Ernst; Dörnemann, Tim; Freisleben, Bernd

doi:10.1109/seaa.2009.15

Cited by 12 publications

(15 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This proposal does not require any change of the original code of the BPEL processes nor of BPEL engine, however it is limited as it supports only the substitution of failing partner services. In [8], E. Juhnke and al. identify classes of faults that can be handled automatically and define a policy language to configure automatic recovery behaviors without the need for adding explicit fault handling mechanisms to the BPEL process.…”

Section: Related Workmentioning

confidence: 99%

Adapting Web Services to Maintain QoS Even When Faults Occur

Cordier¹,

Micalizio²,

Robin³

et al. 2013

2013 IEEE 20th International Conference on Web Services

View full text Add to dashboard Cite

Abstract-The paper addresses the problem of maintaining the quality of service (QoS) of an orchestration of Web services (WS), which can be affected by exogenous events (i.e., faults). The main challenge in dealing with this problem is that typically the service where a failure is detected is not the one where a fault has occurred: faults have cascade effects on the whole orchestration of services. The paper presents a novel methodology to treat the problem that is not based on Web service (re)composition, but on an adaptive re-execution of the original orchestration. Specifically, an orchestrator Manager exploits an abstract representation of the whole orchestration and a diagnostic module to localize the source of the detected failure. Then, the Manager drives the re-execution of the orchestration by deciding which service activities can be skipped, and which others must be re-executed.

show abstract

Section: Related Workmentioning

confidence: 99%

Adapting Web Services to Maintain QoS Even When Faults Occur

Cordier¹,

Micalizio²,

Robin³

et al. 2013

2013 IEEE 20th International Conference on Web Services

View full text Add to dashboard Cite

show abstract

“…Fault tolerance of workflows was investigated by Juhnke et al [7] who implemented a module that is able to transparently handle some faults caused by network or server outages. Here, all Web-service invocations initiated through a BPEL process are intercepted by an extension installed to the BPEL engine.…”

Section: Related Workmentioning

confidence: 99%

Providing fault-tolerant execution of web-service-based workflows within clouds

Behl

Distler

Heisig

et al. 2012

Proceedings of the 2nd International Workshop on Cloud Computing Platforms

View full text Add to dashboard Cite

With a variety of services rapidly evolving at all architectural levels of cloud computing, there is an increasing demand for a standardized way to coordinate their interactions. Business process management, that is, more general, the management of Web-service-based workflows, could satisfy this demand and, indeed, first corresponding o↵erings have gained instant popularity. While from a functional perspective, these Platform-as-a-Service (PaaS) solutions are already quite mature, their support for fault tolerance is still very limited, making them inapplicable for critical tasks.Concerning the deficiencies of currently existing systems, this paper presents a practical solution for executing critical Web-service-based workflows, particularly within clouds, in a fault-tolerant, highly available and highly configurable manner. We achieve this by actively replicating workflows as well as Web services in a combined architecture, reusing existing standard systems and coordination services. By providing an automated transformation tool, replication is realized transparently to existing systems and workflows. Measurements show that our proposed architecture achieves lower response times than existing systems and that the integration of a coordination service imposes only moderate costs, while simplifying the implementation and leading to a dynamically adaptable solution.

show abstract

“…This is inefficient and unsuitable for sporadic operations that only operate on a subset of the entire resources of a system. Another existing recovery method which has potential to do operational recovery is BPEL recovery [6]. BPEL recovery mechanisms treat system workflows as business processes and recover by taking compensating actions for any failures in system workflows [6].…”

Section: Introductionmentioning

confidence: 99%

“…Another existing recovery method which has potential to do operational recovery is BPEL recovery [6]. BPEL recovery mechanisms treat system workflows as business processes and recover by taking compensating actions for any failures in system workflows [6]. However, BPEL's recovery mechanisms usually deal with normal activities of cloud systems, and it requires a BPEL engine to execute [6].…”

Section: Introductionmentioning

confidence: 99%

“…BPEL recovery mechanisms treat system workflows as business processes and recover by taking compensating actions for any failures in system workflows [6]. However, BPEL's recovery mechanisms usually deal with normal activities of cloud systems, and it requires a BPEL engine to execute [6]. Moreover, BPEL recovery has poor generalizability because its recovery installation is specific to a particular system workflow [6].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Process-Oriented Non-intrusive Recovery for Sporadic Operations on Cloud

Zhu

Weber

et al. 2016

2016 46th Annual IEEE/IFIP International Conference on Dependable Systems and Networks (DSN)

View full text Add to dashboard Cite

Cloud-based systems get changed more frequently than traditional systems. These frequent changes involve sporadic operations such as installation and upgrade. Sporadic operations may fail due to the uncertainty of cloud platforms. Each sporadic operation manipulates a number of cloud resources. The accessibility of resources manipulated makes it possible to build an accurate process model of the correct behavior for an operation and its desired effects. This paper proposes a non-intrusive recovery approach for sporadic operations on cloud, called POD-Recovery. POD-Recovery utilizes the above-mentioned process model of the operation. When needed, it triggers recovery actions based on the model through non-intrusive means, i.e., without modifying the code which implements the sporadic operation. POD-Recovery employs an efficient artificial intelligence (AI) planning technique for generating recovery plans. We implement POD-Recovery and evaluate it by recovering from faults injected into 920 runs of five representative sporadic operations.

show abstract

Fault-Tolerant BPEL Workflow Execution via Cloud-Aware Recovery Policies

Cited by 12 publications

References 6 publications

Adapting Web Services to Maintain QoS Even When Faults Occur

Adapting Web Services to Maintain QoS Even When Faults Occur

Providing fault-tolerant execution of web-service-based workflows within clouds

Process-Oriented Non-intrusive Recovery for Sporadic Operations on Cloud

Contact Info

Product

Resources

About