[ 
https://issues.apache.org/jira/browse/AMQ-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rob Davies resolved AMQ-3573.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.6.0

Added warning and error messages is SystemUsage values cannot be met by the 
system.
Changed defaults to:
64mb for memory
50GB for temp store
100GB for store
The GB value was being incorrectly calculated
resolved by SVN revision 1235261
                
> Hardcoded defaults for systemUsage not suitable for out of the box 
> -------------------------------------------------------------------
>
>                 Key: AMQ-3573
>                 URL: https://issues.apache.org/jira/browse/AMQ-3573
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.5.1
>            Reporter: Torsten Mielke
>            Assignee: Rob Davies
>              Labels: default, systemUsage
>             Fix For: 5.6.0
>
>         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 it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to