[
https://issues.apache.org/jira/browse/ARTEMIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023643#comment-15023643
]
ASF subversion and git services commented on ARTEMIS-201:
---------------------------------------------------------
Commit 956c54155f78ec0ee3e89b7c19747e4b89ae2e20 in activemq-artemis's branch
refs/heads/master from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=956c541 ]
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)
