activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (ARTEMIS-201) Log warning if server can crash on OutOfMemory due to "misconfiguration"
Date Thu, 19 Nov 2015 20:59:11 GMT

     [ https://issues.apache.org/jira/browse/ARTEMIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Justin Bertram reassigned ARTEMIS-201:
--------------------------------------

    Assignee: Justin Bertram

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

Mime
View raw message