> > Ah I see. Most clients should send client ACKs async. Waiting for > response for an ack will only buy you the 'and only once' guarantee > MAYBE. You can only get true 'and only once' QOS when you do your > business logic in conjunction with ack in XA mode. Most organizations > are XA adverse (for good reasons) and therefor are willing to accept > duplicate messages (at least once QOS). So this is why acks are > always sent async. Hope that made sense. >
Definitely. I'll modify the client accordingly. I'm wondering if we should change amq stomp behavior so it doesn't send receipts on acks in any case? Cheers -- Dejan Bosanac www.scriptinginjava.net
