Hi, we are performing some tests on our ActiveMq instance (version 5.3.0) and we noticed a memory increase when our persistent queues become quite full of pending messages. The result of slow consumers with producerFlowControl disabled is a constant increase of the memory with the number of pending messages. Analyzing a memory dump in this scenario we noticed that the object org.apache.activemq.broker.region.Queue related to our full queue has a reference to all pending messages. Each org.apache.activemq.broker.region.IndirectMessageReference object linked to queue contains a reference to the original org.apache.activemq.command.ActiveMQTextMessage object with all content (jms message body). What is the reason of caching all the pending object when we work with persistent messages? There is an option we can set to avoid this behaviour?
-- View this message in context: http://old.nabble.com/Persistent-messages-cache-causes-OutOfMemory-tp29106666p29106666.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
