Exception Handling during Asynchronous Method Invocation

Keen, Aaron W.; Olsson, Ronald A.

doi:10.1007/3-540-45706-2_90

Cited by 14 publications

(7 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Regarding exception management in parallel and distributed programming, the exception handling approach proposed by Keen et al [18] for asynchronous method invocation presents similarities with our approach. In the sense that exceptions within the skeleton framework happen in an asynchronous context and we require a predefined handler to manage the exception.…”

Section: Related Workmentioning

confidence: 75%

Exceptions for Algorithmic Skeletons

Leyton

Henrio

Piquer

2010

Euro-Par 2010 - Parallel Processing

View full text Add to dashboard Cite

Abstract. Algorithmic Skeletons offer high-level abstractions for parallel programming based on recurrent parallelism patterns. Patterns can be combined and nested into more complex parallelism behaviors. Programmers fill the skeleton patterns with the functional (business) code, which transforms the generic skeleton into a specific application. However, when the functional code generate exceptions, this exposes the programmer to details of the skeleton library, breaking the high-level abstraction principle. Furthermore, related parallel activities must be stopped as the exception is raised. This paper describes how to handle exceptions in Algorithmic Skeletons without breaking the high-level abstractions of the programming model. We describe both the behavior of the framework in a formal way, and its implementation in Java: the Skandium Library.

show abstract

Section: Related Workmentioning

confidence: 75%

Exceptions for Algorithmic Skeletons

Leyton

Henrio

Piquer

2010

Euro-Par 2010 - Parallel Processing

View full text Add to dashboard Cite

show abstract

“…As replication is transparent to programmers, our exception handling system can easily be compared with other existing EHSs. Various proposals address the issues related to exception handling for active objects integrating asynchronous communication [2,10,3,8,13,14,15,1]. Our solution is original in that it combines the following features: handling of request / response interactions between agents, handling of agent replicas, encapsulation and reactivity, ability to write context-dependent dynamic scope handlers (callercontextualization), ability to coordinate and control groups of active agents collaborating to a common task, ability to configure the exception propagation policy by defining exception resolution functions at the service level.…”

Section: Conclusion and Related Workmentioning

confidence: 99%

Specification of an exception handling system for a replicated agent environment

Dony

Tibermacine

Urtado

et al. 2008

Proceedings of the 4th International Workshop on Exception Handling

View full text Add to dashboard Cite

Exception handling and replication are two mechanisms that increase software reliability. Exception handling helps programmers control situations in which the normal flow of a program execution cannot continue. Replication handles system failures. Exceptions handling and replication do not apply in the same way to the same situations and thus are two complementary mechanisms to increase software reliability. The paper proposes a specification of an execution history oriented exception handling system for an agent language and middleware providing replication. This paper proposes an original signaling algorithm adapted to replicated agents and a rationale of how exception handling and replication mechanisms can combine to increase programmers' capability to achieve reliable agent-based applications.

show abstract

“…A component can create a thread, register a callback, invoke a callback on a thread [4,5], create an asynchronous method [11], make use of thread-specific storage [21] or access a resource requiring thread-affine access, 4 etc. For each of these cases, we created an attribute of the kind described in Section 3.1 expressing the semantics of the case.…”

Section: Threading Modelsmentioning

confidence: 99%

Defining and Checking Deployment Contracts for Software Components

Lau

Ukis

2006

Component-Based Software Engineering

View full text Add to dashboard Cite

Abstract. Ideally in the deployment phase, components should be composable, and their composition checked. Current component models fall short of this ideal. Most models do not allow composition in the deployment phase. Moreover, current models use only deployment descriptors as deployment contracts. These descriptors are not ideal contracts. For one thing, they are only for specific containers, rather than arbitrary execution environments. In any case, they are checked only at runtime, not deployment time. In this paper we present an approach to component deployment which not only defines better deployment contracts but also checks them in the deployment phase.

show abstract

Exception Handling during Asynchronous Method Invocation

Cited by 14 publications

References 4 publications

Exceptions for Algorithmic Skeletons

Exceptions for Algorithmic Skeletons

Specification of an exception handling system for a replicated agent environment

Defining and Checking Deployment Contracts for Software Components

Contact Info

Product

Resources

About