FYI, the only way to ensure that no messages can be lost is to use a transaction. On the provider side, the transaction could span the delivery of the exchange containing the request and the send of the response... In any other case, there may be a time during which the message has been consumed, but not processed.
Cheers, Guillaume Nodet On 4/24/06, Sloan, John L (John) <[EMAIL PROTECTED]> wrote: > ... > What exactly is persistent? I'm guessing that only NMs bound > from a CONSUMER to a PROVIDER may persist, but once the Message > Exchange (ME) is accepted by the PROVIDER, all persistence is > up to the PROVIDER. (I.e. if the system crashes after delivery > of the NM to the PROVIDER, it is the PROVIDER's responsibility > to recover the accepted ME.) It's not clear to me how NMs that > are replies to a request flowing from the PROVIDER to the CONSUMER > can persist since the original ME created by the CONSUMER will > be lost. >
