[rabbitmq-discuss] Workpool memory leak on 3.3.1?

Mon Jun 2 18:07:36 BST 2014

For the most part, with Spring-AMQP, you can avoid having to do manual acks
- use AcknowledgeMode.AUTO (default), set the prefetch (basic.qos) and
txSize to, say, 1000, and the container will send the ack each time 1000
messages are processed (per thread).

http://docs.spring.io/spring-amqp/docs/1.3.4.RELEASE/reference/html/amqp.html#containerAttributes

On Mon, Jun 2, 2014 at 12:24 PM, gui.balde <gperes at daitangroup.com> wrote:

> Hi Michael,
>
> I just shot for 'memory leak' cause I saw it was an issue in the past. I've
> been trying to improve our consumer logic to make it faster/more effective.
> It was good refactoring, but it can only take us too far before we run out
> of memory again.
>
> I'll look into the QoS and manual acks. Those were good tips. Should I have
> any questions, I'll post back.
>
> Thank you very much for your time.
>
> Guilherme.
>
>
>
> --
> View this message in context:
> http://rabbitmq.1065348.n5.nabble.com/Workpool-memory-leak-on-3-3-1-tp35984p35988.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140602/4ccd6dc4/attachment.html>