activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-201) Log warning if server can crash on OutOfMemory due to "misconfiguration"
Date Fri, 20 Nov 2015 15:12:11 GMT


ASF GitHub Bot commented on ARTEMIS-201:

GitHub user jbertram opened a pull request:

    ARTEMIS-201 warn of potential OOME


You can merge this pull request into a Git repository by running:

    $ git pull ARTEMIS-201

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #245
commit f09355bfdad220a300eb46f4474772c57368c30a
Author: jbertram <>
Date:   2015-11-20T02:41:31Z

    ARTEMIS-201 warn of potential OOME


> Log warning if server can crash on OutOfMemory due to "misconfiguration"
> ------------------------------------------------------------------------
>                 Key: ARTEMIS-201
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 1.0.0
>            Reporter: Miroslav Novak
>            Assignee: Justin Bertram
>             Fix For: 1.1.1
> Imagine situation where server is started with 3000 destinations and max-size-bytes is
set to 10MB. This would mean that JVM would have to be started with at least 30GB of memory
to prevent OOM in case that all destinations get filled up. (PAGE mode is not a solution in
this case as it starts once destination exceeds 10MB in memory)
> Purpose of this jira is to provide check which would print warning in case that such
OOM can happen. This check would be executed during start of server and then with adding any
destination at runtime.

This message was sent by Atlassian JIRA

View raw message