[ 
https://issues.apache.org/jira/browse/AMQ-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964977#comment-14964977
 ] 

ASF subversion and git services commented on AMQ-3573:
------------------------------------------------------

Commit dc19d28af92a5fce4969352c53f02b11ee3f59e9 in activemq's branch 
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=dc19d28 ]

 https://issues.apache.org/jira/browse/AMQ-3573  
https://issues.apache.org/jira/browse/AMQ-2834 - only validate limits if they 
are set


> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to