Issue - R27 - Faults and Parallelism in Termination Handlers

[ws-bpel issues list editor<peter@furniss.co.uk>]

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if a motion to open the issue is proposed and that motion is approved by the TC. A motion could also be proposed to close it without further consideration. Otherwise it will remain as "received".

The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent version of the document entitled in the "Issues" folder of the WSBPEL TC document list - the next posting as a TC document will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.

Issue - R27 - Faults and Parallelism in Termination Handlers

Status: received
Date added: 30 Oct 2006
Date submitted: 27 October 2006
Submitter: Dieter Koenig
Description: Consider the following examples of parallelism inside of
termination handlers.

Example 1. Assume that a custom termination handler contains a parallel forEach activity or a flow activity. In either case, assume that multiple concurrent branches are active. If one branch faults, the specification does not tell whether the other branches are allowed to complete or terminated.

Example 2. Assume that a default termination handler that compensates a compensation handler instance group. If one compensation handler instance faults, the specification does not tell whether the other compensation handler instances are allowed to complete or terminated.
Submitter's proposal: Add the following to the end of section 12.6.:

> "If a custom termination handler contains parallel activities and one of
> these activities propagates a fault then all concurrent activities in
> the termination handler MUST be terminated. Likewise, if a default
> termination handler compensates a compensation handler instance group
> and one of the compensation handler instances propagates a fault then
> the other compensation handler instances of the compensation handler
> instance group MUST be terminated."

Changes: 30 Oct 2006 - new issue

---

To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the wsbpel@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - R27 - [anything]" or is a reply to such a message. If you want to formally propose a resolution to an open issue, please start the subject line "Issue - R27 - Proposed resolution", without any Re: or similar.

To add a new issue, see the issues procedures document