Re: [ws-rx] [NEW ISSUE] Rollover underspecified, state of sequenceis unclear

[Paul Fremantle <paul@wso2.com>]

Doug/Bob

Yep we had this already. Issue number 111

http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i111

Paul


Doug Davis wrote:
>
> Bob,
>   if a MsgNumRollover fault is generated I don't think the RMD should 
> necessarily terminate the sequence.There may be other messages, with 
> lower numbers, that could still be received and processed 
> successfully.  Didn't we discuss this already - it sounds familiar.
> -Doug
>
>
>
> *"Bob Freund-Hitachi" <bob.freund@hitachisoftware.com>*
>
> 06/26/2006 11:33 AM
>
> 	
> To
> 	"[WS-RX]" <ws-rx@lists.oasis-open.org>
> cc
> 	
> Subject
> 	[ws-rx] [NEW ISSUE] Rollover underspecified, state of sequence is 
> unclear
>
>
>
> 	
>
>
>
>
>
> *Description*
>  
> WD 15 lines 564-570 state that if the internal limitation for 
> MessageNumber is exceeded by either RMS or RMS, then a 
> MessageNumberRollover fault is generated.
> Section 4.5 which describes the fault provides no further information
>  
>  
> *Justification *
>  
> Possibility for protocol lockup or non-interoperable behavior
>  
>  
> Target: core
>  
> *Proposal: *
>  
> Insert after line 570:
> Generation or receipt of a MessageNumberRollover fault MUST 
> immediately terminate the sequence
>  
> Insert in section 4.5
>  
> Sent by: RMS or RMD
> Condition: message numbers for a Sequence have been exhausted
> Action upon Generation or receipt: The Sequence is terminated 
> immediately.


-- 

Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://feeds.feedburner.com/bloglines/pzf
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com