OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-tx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [Fwd: Issue 041: Inconsistent Internal State]


Third reposting

-------- Original Message --------
Subject: Issue 041: Inconsistent Internal State
Date: Tue, 01 Aug 2006 07:31:11 +0100
From: Alastair Green <alastair.green@choreology.com>
To: ws-tx@lists.oasis-open.org <ws-tx@lists.oasis-open.org>


Inconsistent Internal State is defined thus:

"This fault is sent by a participant to indicate that it cannot fulfill 
its obligations.  This indicates a global consistency failure and is an 
unrecoverable condition."

It is only used, in fact, to mean: "Coordinator has already instructed 
participant to Commit or Rollback, but is now saying the opposite".

This is a condition that simply cannot arise, other than by bug. A 2PC 
coordinator cannot change its mind once it has issued an outcome message.

What is so special about this bug, that it requires its very own fault type?

Alastair





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]