[rabbitmq-discuss] Publish and ACK in different channels

[Alexandru Scvorţov]

I'm not familiar with Thrift, so I cannot really answer.

A simple solution would be to basic.get with noAck set to true.  That
way, messages will be not need to be acknowledged (so they won't get
redelivered).

If you really need the client to be the one ack'ing the message (perhaps
because you sometimes do want the message to be redelivered), I think
you'll have to short-circuit Thrift.

Cheers,
Alex

On Wed, Aug 11, 2010 at 03:11:14PM +0530, Abhishek K wrote:
> In my situation
> I am using a thrift layer in the middle.
> RabbitMQ runs on Machine A, Thrift on Machine B and Client on Machine C.
> Thrift is the middle layer, which relays the message to the client.
> 
> Now if I have to acknowledge the message I have to keep the channel object
> open at the Thrift layer, till the user acknowledges the message.
> What can be the best way to do this.
> 
> Thanks
> Abhishek Kona
> 
> 
> On Wed, Aug 11, 2010 at 3:02 PM, Alexandru Scvorţov
> <alexandru at rabbitmq.com>wrote:
> 
> > If you get a message and close the channel without ack'ing it, the
> > message will get reinserted into the queue.
> >
> > If you don't want the message to be reinserted, either you acknowledge
> > it explicitly, or you get with noAck set to true.
> >
> > Cheers,
> > Alex
> >
> > On Wed, Aug 11, 2010 at 02:31:40PM +0530, Abhishek K wrote:
> > > I am using the RabbitMQ Java API.
> > >
> > > Channel A does a basicGet, gets message M channel A is closed. AutoAck is
> > > set to false.
> > > Now I need to Ack message M using some other channel (channel B), and do
> > not
> > > want message M to be delivered to some other consumer in the meanwhile.
> > What
> > > can be the best approach to achieve this?
> > >
> > > Abhishek Kona
> > > Department of Computer Engineering
> > > National Institute of Technology
> > > Karnataka, India
> >
> > > _______________________________________________
> > > rabbitmq-discuss mailing list
> > > rabbitmq-discuss at lists.rabbitmq.com
> > > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> >
> >