[rabbitmq-discuss] Unacked msgs in Dureable Q

[m.luchak at smartasking.com]

Hi Emile,
 
Thanks for your reply.. Unfortunately, it is impossible for us to guarantee that a msg will be acked by the same channel.  We are connected to tcp over 3G so we're lucky if the connection is up for 45 secs...
 
Can you give me an idea how serious a problem, performance wise,  it is to have the msgs unacked like this?
 
 


OverviewMessagesMessage rates
NameExclusiveParametersStatusReady▲ UnackedTotalincomingdeliver / getack
[http://ec2-177-71-233-182.sa-east-1.compute.amazonaws.com:55672/#/queues/%2F/bbmatteo_bbmatteo] myQueueDIdle0104010400.00/s
[http://ec2-177-71-233-182.sa-east-1.compute.amazonaws.com:55672/#/queues/%2F/smart60_smart60] yourQueueDIdle02152150.00/s
[http://ec2-177-71-233-182.sa-east-1.compute.amazonaws.com:55672/#/queues/%2F/felipeteste_felipeteste] notMyQueueDIdle020200.00/s
 
-----Original Message-----
From: "Emile Joubert" <emile at rabbitmq.com>
Sent: Wednesday, November 14, 2012 10:52am
To: "Discussions about RabbitMQ" <rabbitmq-discuss at lists.rabbitmq.com>
Cc: m.luchak at smartasking.com
Subject: Re: [rabbitmq-discuss] Unacked msgs in Dureable Q



Hi Matthew,

On 14/11/12 11:48, m.luchak at smartasking.com wrote:
> qConsumer.getChannel().basicAck(msg.getDeliveryTag(), false);
>
> This "seems" to be working fine but the msgs are remaining Unacked....

The number of unacknowledged messages in the queue should decrease by 1 
when you successfully acknowledge a message:

 $ rabbitmqctl list_queues name messages_unacknowledged

> Could this be because it is not always the same consumer that first
> received the msgs that is doing the acking?
It is important that messages be acknowledged on the same channel as the 
channel they were received on.



-Emile



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121114/a007a059/attachment.htm>