activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Klaus Pittig <>
Subject How to avoid blocking of queue browsing after ActiveMQ checkpoint call
Date Fri, 08 Jan 2016 15:27:27 GMT
(related issue:

There's a problem when Using ActiveMQ with a large number of Persistence
Queues (250) á 1000 persistent TextMessages á 10 KB.

Our scenario requires these messages to remain in the storage over a
long time (days), until they are consumed (large amounts of data are
staged for distribution for many consumer, that could be offline for
some days).

After the Persistence Store is filled with these Messages and after a
broker restart we can browse/consume some Queues  _until_ the
#checkpoint call after 30 seconds.

This call causes the broker to use all available memory and never
releases it for other tasks such as Queue browse/consume. Internally the
MessageCursor seems to decide, that there is not enough memory and stops
delivery of queue content to browsers/consumers.

=> Is there a way to avoid this behaviour by configuration or is this a bug?

The expectation is, that we can consume/browse any queue under all

Settings below are in production for some time now and several
recommendations are applied found in the ActiveMQ documentation
(destination policies, systemUsage, persistence store options etc.)

 - Behaviour is tested with ActiveMQ: 5.11.2, 5.13.0 and 5.5.1.
 - Memory Settings: Xmx=1024m
 - Java: 1.8 or 1.7
 - OS: Windows, MacOS, Linux
 - PersistenceAdapter: KahaDB or LevelDB
 - Disc: enough free space (200 GB) and physical memory (16 GB max).

Besides the above mentioned settings we use the following settings for
the broker (btw: changing the memoryLimit to a lower value like 1mb does
not change the situation):

                <policyEntry queue=">" producerFlowControl="false"
optimizedDispatch="true" memoryLimit="128mb"
                        <strictOrderDispatchPolicy />
                        <storeCursor />
        <systemUsage sendFailIfNoSpace="true">
                <memoryUsage limit="50 mb" />
                <storeUsage limit="80000 mb" />
                <tempUsage limit="1000 mb" />

If we set the **cursorMemoryHighWaterMark** in the destinationPolicy to
a higher value like **150** or **600** depending on the difference
between memoryUsage and the available heap space relieves the situation
a bit for a workaround, but this is not really an option for production
systems in my point of view.

Screenie with information from Oracle Mission Control showing those
ActiveMQTextMessage instances that are never released from memory:


View raw message