[
https://issues.apache.org/jira/browse/ARTEMIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022497#comment-15022497
]
ASF GitHub Bot commented on ARTEMIS-201:
----------------------------------------
Github user clebertsuconic commented on the pull request:
https://github.com/apache/activemq-artemis/pull/245#issuecomment-158999892
@jbertram think the following:
An user sets 100 destinations.. with 100M cache... the memory would be able
to fit only 10 paged destinations..
The user has monitoring in place... whenever a consumer drops and page
increases he will take action and restart the client...
that means... he would make sure he wouldn't get to the 100 paged message
using monitoring tools...
That's a valid scenario.. with your messages users will assume they must
have memory available at all times.
> 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)
