[kombu] Unexpected behaviour in consumer using connection pools

34 views
Skip to first unread message

Alfonso Acosta

unread,
Feb 13, 2014, 7:40:13 PM2/13/14
to carrot...@googlegroups.com
Hi,

I wrote a consumer which uses connection pool. However, to my surprise, it only pops (acks) one message from the RabbitMQ queue (i.e. on_message is only called once). The rest are left unacknowledged and returned to the queue once the program terminates.

Here's a selfcontained program which shows the aforementioned behaviour:


If I use dedicated a dedicated connection instead of a connection pool, al messages are popped. 

Any help would be appreciated. Thanks,

Alfonso Acosta



Reply all
Reply to author
Forward
0 new messages