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: i144 - Editorial (maybe) RMS MessageNumberRollover behavior unclear



http://lists.oasis-open.org/archives/ws-rx/200606/msg00212.html

Bob,
  Just to get the discussion going on this (again), I would prefer to close this with no action.  Your two questions:

1) It is unclear under what circumstances the RM Source generates a MessageNumberRollover fault
2) Assuming that the RM Destination Transmits a MessageNumberRollover fault upon receipt of a message with a MessageNumber that exceeds its internal limitations or the big number cited, whichever happens first, what mechanism is used by the RM Source to close or terminate the sequence?

Are either already covered in the spec or are implementation choices/details that the spec should not dictate.
For (1) the RMS may choose to generate this if the AS asks to use a msg# that is too big.  But this is not something the spec can (or should) have any say over.  This is not something that would appear on the wire and is an issue between the AS and the RMS.  I would point out that in the case of the AS trying to use a msg # that is too big (if the RMS allows the AS this choice at all), could result in some other fault too.  Since the RM spec deals with just faults related to the RM protocol, and this fault is not necessarily an RM protocol fault, there is no reason to mandate a specific fault for this condition.
If your (1) was related to whether or not an RMS passes a MsgNumRollover fault that it received from the RMD back up to the AS (so it is in essence generating a MsgNumRollover fault on behalf of the RMD) then again this is an impl detail.  The RMS may choose to never expose this fault to the AS - we can't say.

For (2) - why do you assume that the RMS should close or terminate the sequence?  There are other choices - like start a new sequence for that msg.

thanks
-Doug


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