On 02/18/2016 02:24 PM, Hiram Chirino wrote: > I thought that ACKs were supposed to be transactional per the spec. That was my understanding as well, here's the relevant text from the spec.
"|ACK| is used to acknowledge consumption of a message from a subscription using |client| or |client-individual| acknowledgment. Any messages received from such a subscription will not be considered to have been consumed until the message has been acknowledged via an |ACK|. The |ACK| frame MUST include an |id| header matching the |ack| header of the |MESSAGE| being acknowledged. Optionally, a |transaction| header MAY be specified, indicating that the message acknowledgment SHOULD be part of the named transaction." > On Thursday, February 18, 2016, Clebert Suconic <[email protected]> > wrote: > >> TBH I don't remember what Hiram (et all) wrote on the spec. It will be >> a bug depending on what's said at the spec. >> >> On Thu, Feb 18, 2016 at 9:43 AM, Lionel Cons <[email protected] >> <javascript:;>> wrote: >>> The Artemis 1.2.0 doc contains: >>> >>> | Message acknowledgements are not transactional. The ACK frame can not >> be part >>> | of a transaction (it will be ignored if its transaction header is >> set). >>> Is this a design decision (meaning that this behaviour will not change) >> or is >>> this considered as a bug (that will be fixed at some point)? >>> >>> In the latter case, it would be good to create a Jira issue for this to >> track >>> its progress (I didn't find any related issue in Jira). >>> >>> Cheers, >>> >>> Lionel >> >> >> -- >> Clebert Suconic >> > -- Tim Bish twitter: @tabish121 blog: http://timbish.blogspot.com/
