[rabbitmq-discuss] Looking for clarification on acknowledgements, channels, and connections

Alexis Richardson alexis at rabbitmq.com
Wed Mar 7 20:25:10 GMT 2012


Matt

Could you achieve what you want by lifting 'ack' to the application layer?

alexis


On Wed, Mar 7, 2012 at 8:20 PM, Simone Busoli <simone.busoli at gmail.com> wrote:
> Hi Matt, your understanding is correct, acknowledgements are meaningful only
> within the context of the same channel, therefore the answer to your last
> question is no.
> If the connection bounces or the channel closes for any other reasons you
> should not acknowledge the messages your consumer was delivered already and
> just assume they will be redelivered to the next consumer which will start
> consuming to the same queue.
>
> On Wed, Mar 7, 2012 at 21:00, Matt Pietrek <mpietrek at skytap.com> wrote:
>>
>> I thought I understood this topic clearly, but some recent experiences
>> have me seeking more info, as I can't find this exact topic explicitly
>> described.
>>
>> When a message is delivered on a particular connection/channel
>> combination, can it ever be successfully acknowledged on a different
>> connection?
>>
>> My current understanding is "no".
>>
>> Some background: In our messaging layer, we want to hide the connection
>> drops from the upper application layer. That is, if we try to use a
>> previously working connection/channel, and it fails, we'll simply catch the
>> exception and try to reconnect.
>>
>> So the question is, after the reconnect, should we even attempt to
>> acknowledge messages read from the original connection?
>>
>>
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>


More information about the rabbitmq-discuss mailing list