Return-Path: 
 <dev-return-29300-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A331379A2
	for <apmail-activemq-dev-archive@www.apache.org>;
 Thu,  3 Nov 2011 10:21:53 +0000 (UTC)
Received: (qmail 17395 invoked by uid 500); 3 Nov 2011 10:21:53 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 17356 invoked by uid 500); 3 Nov 2011 10:21:53 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 17347 invoked by uid 99); 3 Nov 2011 10:21:53 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2011 10:21:53 +0000
X-ASF-Spam-Status: No, hits=-2001.2 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2011 10:21:52 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 3823132F711
	for <dev@activemq.apache.org>; Thu,  3 Nov 2011 10:21:32 +0000 (UTC)
Date: Thu, 3 Nov 2011 10:21:32 +0000 (UTC)
From: "Torsten Mielke (Commented) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <654935503.55108.1320315692231.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <879030981.49940.1320228212260.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3573) Hardcoded defaults for systemUsage
 not suitable for out of the box
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Torsten Mielke commented on AMQ-3573:
-------------------------------------

Thanks for your input Gary. 
I have repeatedly seen companies deploying ActiveMQ in production where the underlying disk had only 10-30 GB of free space left. 
Just this week I found a company that deployed ActiveMQ with almost default settings (commented <systemUsage> in ActiveMQ) and they only had 6 GB of hard disk space available. 
I believe this happens fairly often. 

I can see that the limits I proposed may seem a bit low but assuming there will be up to 110GB disk space available by default may be too much? 
Also, this will not be apparent from looking at the default conf (see AMQ-3574). So I presume most users of ActiveMQ are unaware of these high default limits.

                
> 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
>              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 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