[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue 043 - WS-AT: Invalid state inappropriate response to orphaned volatile participants
This is identified as WS-TX issue
043. Please ensure follow-ups have a subject line starting
"Issue 043 - WS-AT: Invalid state inappropriate
response to orphaned volatile participants". From: Peter Furniss
[mailto:peter.furniss@erebor.co.uk] Issue name -- WS-AT: Invalid state inappropriate
response to orphaned volatile participants PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON
THREAD UNTIL THE ISSUE IS ASSIGNED A NUMBER. The issues coordinators will notify the list when that has
occurred. Target document and draft: Protocol: WS-AT Volatile 2PC Artifact: spec Draft: AT spec cd 1 Link to the document referenced: Section and PDF line number: section 10, lines 503/505 tables rows Prepared, Relay,
column None
Design
New issue: Coordinator should not distinguish protocol of
orphaned participants Issue Description: The use of Issue Details Background - see separate issue : Coordinator should
not distinguish protocol of orphaned participants
Occurence of InvalidState according to this definition, and
in all its other occurrences in the state tables for WS-AT or WS-BA imply that
one or other of the implementations is bugged. It is to be expected that
implementations would report such a fault conspicuously. This is an inappropriate message in this instance. The
meaning the coordinator needs to send to the participant is something like:
"Legitimate message received, but transaction outcome is unknown: I can't
help you". Since the volatile participant, by definition, doesn't
care very much, implementations will not want to contaminate their error logs
with reporting these occurrences, which can occur between fully correct implementations.
They will either have to insert special code to identify this circumstance or
annoy their users. Proposed resolution Use a new message, as proposed for issue WS-AT: Coordinator
should not distinguish protocol of orphaned participants |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]