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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-tx-implement message

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


Subject: Q on scenario 5.1



The text in the interop doc for scenario 5.1 is a bit mixed up.  The extra text talks about 2 PS's but the message flow section only talks about one PS.  Am I correct that this scenario only has one PS?

thanks

-Doug

5.1 ReplayCommit.

Description: PA registers PS1 and PS2 for Durable2PC, IA initiates commit, PS2 suffers from internal recoverable failure after receiving Durable2PC::Commit, sends 2PC::Prepared back to Coordinator upon recovery. Transaction is Committed.

Initialization

IA sends an application message tns:ReplayCommit request to PA containing CoordinationContext.
PA registers PS with CS for a Durable2PC protocol.
PA responds with an application reply tns:Response.
Message Exchange

        (IA initiates Commit)

CS sends Durable2PC::Prepare to PS
PS sends Durable2PC::Prepared to CS
CS sends Durable2PC::Commit to PS
(PS suffers from internal failure)
(PA prevents any re-sent Commit from reaching PS)

Upon recovery, PS sends 2PC::Prepared to CS
CS re-sends Durable2PC::Commit to PS
PS sends Durable2PC::Committed to CS

Success Criteria

CS receives 2PC::Prepared (second one) from PS2 AND CS receives Durable2PC::Committed from PS2.

State Diagram Coverage of the 2PC protocol

Scenario covers the following (State, Event):

Coordinator (for PS2):
    (Active, Register), (Preparing, Prepared), (Committing, Prepared), (Committing, Committed)

Participant (PS2): (None, RegisterResponse), (Active, Prepare), (PreparedSuccess, Commit)



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