[
https://issues.apache.org/jira/browse/ARTEMIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022544#comment-15022544
]
ASF GitHub Bot commented on ARTEMIS-201:
----------------------------------------
Github user jbertram commented on the pull request:
https://github.com/apache/activemq-artemis/pull/245#issuecomment-159003967
Even though they have monitoring in place to avoid the OOME, the OOME is
still possible if something were to malfunction with regards to the monitoring.
I think the WARN is still valid. The broker has no way of knowing how it's
actually going to be used. It only knows how it has been configured. Users
can (and do) ignore WARN messages all the time when they know the messages
don't apply to their use-case, but that doesn't mean the WARN messages aren't
valid for lots of other use-cases.
> 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)
