[rabbitmq-discuss] Workpool memory leak on 3.3.1?
gperes at daitangroup.com
Mon Jun 2 15:40:19 BST 2014
I know this was a known issue back with 2.7.1
We've been profiling one of our modules running on an ec2 instance consuming
from a rabbit queue.
The message consumer simply queues the delivered object as a task to be
consumed by an internal thread, no hassle.
This internal thread takes each item from the internal queue and goes over
the wire to the database. This takes time due to net i/o and transactions.
This makes our consumer a slow consumer ;)
In this scenario we expected to see messages queueing up on "rabbitmqctl
list_queues", but instead, we see none. What we see is the workPool (inside
com.rabbitmq.client.impl.ConsumerWorkService) filling up to 780MB of items
in the 'pool' HashMap. Which then leads to an OutOfMemoryError when under a
We currently have 90 consumers synchronizing that one internal queue I
Does anyone see any problems here?
Thanks in advance.
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Workpool-memory-leak-on-3-3-1-tp35984.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
More information about the rabbitmq-discuss