[
https://issues.apache.org/jira/browse/ARTEMIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018134#comment-15018134
]
ASF GitHub Bot commented on ARTEMIS-201:
----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/245
ARTEMIS-201 warn of potential OOME
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-201
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/245.patch
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 <[email protected]>
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: https://issues.apache.org/jira/browse/ARTEMIS-201
> 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
(v6.3.4#6332)
