[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue - 16 - Ensuring exactly once
This issue has been added to the wsbpel issue list. It is in the current version of the list at wsbpel document 2656, It is hoped to have a fixed url for the ever-changing list.
2. Process B is defined with a receive instruction corresponding to the invoke of process A, and the receive instruction creates a new instance of the process. So upon receipt of the message from process A, a new instance of process B is created, and this instance executes the receive instruction.
3. The machine hosting process A crashes.
4. Process B executes the next step, which is to debit an account and update a database.
5. Process B terminates. Process B has finished.
6. The machine hosting process A is restarted. Process A then
re-executes the invoke instruction.
On step 6, how can we prevent process A from executing the invoke a
second time, creating another instance of process B, and debiting the
account a second time?
To comment on this issue, please follow-up to this announcement on the wsbpel-reqts@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 - 16 - [anything]".
To add a new issue, send email to the wsbpel requirements and issues coordination list, adding a proposed title for the issue to the subject line. See the issues procedures document for further information.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]