[rabbitmq-discuss] [rabbitmq-c] amqp_queue_unbind eat a lot of memory in some usecases

• Previous message: [rabbitmq-discuss] [rabbitmq-c] amqp_queue_unbind eat a lot of memory in some usecases
• Next message: [rabbitmq-discuss] [rabbitmq-c] amqp_queue_unbind eat a lot of memory in some usecases
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Alan, thanks for your reply.

I set no-ack to 0 in basic.consume, so I suggest that server will wait for
basic.ack from client on each message. Or I have to set no-ack to 1 for this
behaviour?



--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/rabbitmq-c-amqp-queue-unbind-eat-a-lot-of-memory-in-some-usecases-tp29384p29393.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

• Previous message: [rabbitmq-discuss] [rabbitmq-c] amqp_queue_unbind eat a lot of memory in some usecases
• Next message: [rabbitmq-discuss] [rabbitmq-c] amqp_queue_unbind eat a lot of memory in some usecases
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]