David, I am not sure that I agree with this. I thought that persistentDuration was related to a specific message. I am thinking about the case when the intermediate message may be a price quote and the price quote is only valid for a few hours. The persistDuration would be set to expire after the termination of the validity period for the quote. However, the conversation would still be open. I can think of several business cases where the persistDuration makes sense on a per message basis (not to be confused with perMessage) and not based on the conversation. Ralph Berwanger David Fischer wrote: > I seem to be missing something. The end of a conversation is controlled by > persistDuration, isn't it? I think the ConversationId is held in persistent > store with the MessageId (at least in the case of MessageOrdering). Along with, > or in, the MessageId record, there must be a persistDuration field. When the > last message in that conversation is deleted from the persistent store > (persistDuration has passed), wouldn't the ConversationId automatically go with > it? If there are still messages waiting because they are out of order, would > they not also be deleted when persistDuration expires? If you are concerned > with messages going away too quickly, then make persistDuration long. > > There is nothing forbidding another later message to be sent with the original > ConversationId but the message order would not be of concern since all the > previous messages have expired anyway. > > Or, are you saying ConversationId is held somewhere else? > > Regards, > > David Fischer > Drummond Group. > >