You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2015/11/20 00:03:11 UTC

[jira] [Commented] (ARTEMIS-201) Log warning if server can crash on OutOfMemory due to "misconfiguration"

    [ https://issues.apache.org/jira/browse/ARTEMIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014674#comment-15014674 ] 

Justin Bertram commented on ARTEMIS-201:
----------------------------------------

I will add this check for when the server is started. 

For memory related warnings during runtime the user can configure a memory-measure-interval > 0 and an appropriate memory-warning-threshold.

> 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
>
> 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)