Good afternoon,

Trying to overcome some performance issues I am experiencing on my lab and 
hoping this distro can assist. Running version 7.0. My overall config is a VM 
with 32GB of memory and 8 cores. I have my java -Xmx  set to use 24GB.

With a fairly out of the box config, we could run for about an hour before amq 
ran out of memory and started to hang.
I then went into the config and setup some defaults for all of our queues such 
as:

broker.xml
<persistence-enabled>false</persistence-enabled>true
<paging-directory>data/paging</paging-directory>

<address-setting match="#">
<dead-letter-address>DLQ</dead-letter-address>
<expiry-address>ExpiryQ</expiry>
<expiry-delay>1000000</expiry>
<send-to-dla-on-no-route>false</send-to-dla-on-no-route>
<max-size-bytes>-1</max-size-bytes>
<page-size-bytes>10000000</page-size-bytes>
<address-full-policy>PAGE</address-full-policy>
</address-settings>


In my head, this would cause all messages on all queues to become Expired after 
100 seconds. This would then go to the ExpiryQ. At this point the Expiry reaper 
thread would clean them up thus freeing up memory. 

This doesn't seem to be the case as it is still using all of the memory within 
about an hour. Am I missing a specific option to help with cleanup of expired 
messages to not consume all of the memory? Or am I doing something incorrectly? 
Thanks. 

Also - Would paging be a benefit for this? I have it disabled I believe via the 
"persistence-enabled" false flag I believe. 

Reply via email to