Skip to main navigation Skip to search Skip to main content

Robust client/server shared state interactions of collaborative process with system crash and network failures

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

298 Downloads (Pure)

Abstract

With the possibility of system crashes and network failures, the design of robust client/server interactions for collaborative process execution is a challenge. If a business process changes state, it sends messages to relevant processes to inform about this change. However, server crashes and network failures may result in loss of messages. In this case, the state change is performed by one party, resulting in state/behavior inconsistencies and possibly deadlocks. Our basic idea to solve the problem is to cache the response (in a synchronous interaction) if the state of the process instance has changed by the request message. The possible state inconsistencies are recognized and compensated by state-caching and retrying failed interactions. By doing this work, we have learnt the possible failures caused by system crashes and network failures. Our results make it possible to build robust interactions by cached-based process transformations.
Original languageEnglish
Title of host publication10th IEEE Internaional Conference on Services Computing, SCC 2013
Place of PublicationPiscataway, NJ, USA
PublisherIEEE
Pages192-199
Number of pages8
ISBN (Print)978-0-7695-5026-8
DOIs
Publication statusPublished - Jun 2013
EventIEEE 10th Internaional Conference on Services Computing, SCC 2013 - Santa Clara Marriott, United States
Duration: 27 Jun 20132 Jul 2013
Conference number: 10

Conference

ConferenceIEEE 10th Internaional Conference on Services Computing, SCC 2013
Abbreviated titleSCC
Country/TerritoryUnited States
CitySanta Clara Marriott
Period27/06/132/07/13

Keywords

  • 2020 OA procedure
  • SCS-Services

Fingerprint

Dive into the research topics of 'Robust client/server shared state interactions of collaborative process with system crash and network failures'. Together they form a unique fingerprint.

Cite this