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


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

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

Subject: Re: [ws-rx] NEW ISSUE: Sequence termination on Fault


I am a bit confused.  Rolling over a message sequence number and 
preserving the original sequence does absolutely nothing to reclaim 
resources or mitigate the problem of superseding the destinations 

Assume for example that the rollover was at 1000 and message 1001 is now 
the new 0001.  In order to facilitate reliable messaging, the 
destination still has to preserve all 1000 of the original message plus 
reconcile message 0001 as message 1001, not have duplicate message 
0001's in the sequence.  Since the messaging component of the stack is 
relatively dumb and will get its instructions for things like rolling 
back transactions form the application/business layer, it cannot release 
the first 1000 messages since the upper stack logic may dictate that if 
message 1003 is not received in XX minutes, the entire sequence should 
roll back to message 934.  Accordingly, it must persist all messages in 
the sequence or throw an unrecoverable fault.

The rollover is currently an unrecoverable fault and nothing more.   
That is how it is written in the current draft.

Did I miss something?  Please correct me if I did.


Duane Nickull

Paul Fremantle wrote:

>I think Jacques' points about handling the rollover problem "smoothly" are
>key. I would like to see an explicit sequence take-over model that can be
>used to preserve ordering across sequences where one sequence has ended -
>prematurely from the RM sources perspective.

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