activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Mielke (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-3738) Cursors not dealing with topic memoryLimit overflow
Date Tue, 28 Feb 2012 09:53:49 GMT


Torsten Mielke commented on AMQ-3738:

IIRC then producer flow control will kick in. Paging out to disk only happens when 100% of
the memoryLimit are used. At that same time producer flow control will kick in as well because
of the 100% limit being reached. Paging to disk will only occur if producer flow control is
But I presume the limit at which paging to disk happens may be configurable.
> Cursors not dealing with topic memoryLimit overflow
> ---------------------------------------------------
>                 Key: AMQ-3738
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: OSX, Apple Java Runtime 1.6.0_26
>            Reporter: Jakub Korab
>         Attachments: activemq-cursors.xml, pom.xml
> I have defined a topic with a memoryLimit of 1mb using a fileDurableSubscriberCursor.
I would expect that sending messages to a durable subscriber through that topic would result
in more than 1mb worth of messages being able to be sent. Instead producer flow control kicks
in at the 1mb limit. 
> To test this I am using the Maven activemq-perf plugin with a single consumer and producer:
> $ mvn activemq-perf:producer -Durl=tcp://localhost:61616 -Dproducer.destName=topic://orders
> $ mvn activemq-perf:consumer -Durl=tcp://localhost:61616 -Dconsumer.durable=true -Dconsumer.destName=topic://orders
> This does not match the behaviour described in
> Going by the docs, I would expect messages to get paged out to disk until the systemUsage/tempUsage
limit fills up.
> This same behaviour happens using the default cursor configuration.
> Attached are the activemq-perf pom and activemq.xml.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message