activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-3573) Hardcoded defaults for systemUsage not suitable for out of the box
Date Thu, 03 Nov 2011 00:21:34 GMT


Gary Tully commented on AMQ-3573:

not sure I agree. Large disks are the norm and I think it is better to have the broker spool
to disk for as long as it can rather than block pending some arbitrary small limit. I guess
making small limits would make users more aware of them, but with the existing values most
users can simply ignore them.

> Hardcoded defaults for systemUsage not suitable for out of the box 
> -------------------------------------------------------------------
>                 Key: AMQ-3573
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.5.1
>            Reporter: Torsten Mielke
>              Labels: default, systemUsage
>         Attachments: AMQ-3573.patch
> Right now the default activemq.xml has the entire <systemUsage> section commented
out. If commented, then the default systemUsage as defined in BrokerService.getSystemUsage()
applies and uses these limits:
> memoryLimit 64 MB
> storeLimit: 10 GB
> tempLimit: 100 GB
> I don't think these are good default values as in the worst case the broker may use 110
GB of disk space. Many runtime environments will not have that much disk space and are therefore
in danger of running out of disk space completely. 
> IMHO some more sensitive defaults would be 
> memoryLimit 64 MB
> storeLimit:  1 GB
> tempLimit:   1 GB
> to prevent the broker from using too much disk space by default. 
> I believe most users of ActiveMQ are unaware of these defaults and probably don't expect
the broker to use up to 110 GB of their disk. 
> If anyone really needs large store and temp limit, they should explicitly configure for

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