David,
I agree with what you are quoting but there is another place which states
that when persistDuration expires, a delivery failure is to be declared.
My point was that because of the way Retries and RetryInterval are defined,
persistDuration may run out before all the permitted retries have been
completed, potentially leading to a delivery failure that might be
replacing a later successful retry.
Regards,
Marty
*************************************************************************************
Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287; IBM tie line 863-7287
Notes address: Martin W Sachs/Watson/IBM
Internet address: mwsachs @ us.ibm.com
*************************************************************************************
"Burdett, David" <david.burdett@commerceone.com> on 07/26/2001 12:12:38 PM
To: "'christopher ferris'" <chris.ferris@east.sun.com>, Martin W
Sachs/Watson/IBM@IBMUS
cc: ebxml-cppa@lists.oasis-open.org, ebxml-msg@lists.oasis-open.org
Subject: RE: persistDuration and retries
Marty
Your definition oif persistDuration is not quite correct. It should be
(quoting from section 10.2.8)
>>>The persistDuration value is the minimum length of time, expressed as a
[XMLSchema] timeDuration, that data from a reliably sent Message, is kept
in
Persistent Storage by a Receiving MSH.<<<
David