[
https://issues.apache.org/jira/browse/ARTEMIS-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671251#comment-16671251
]
ASF GitHub Bot commented on ARTEMIS-1710:
-----------------------------------------
Github user lulf commented on the issue:
https://github.com/apache/activemq-artemis/pull/2401
@michaelandrepearce @mtaylor Ok, just to make sure I understand this, what
we have today:
```
<global-max-size>-1</global-max-size>
```
would be equivalent to:
```
#
<accumulative-max-size>-1</accumulative-max-size>
```
Which would give the same 1/2 JVM heap as the max size.
And to avoid restrictions on activemq.management we would set:
```
#
<accumulative-max-size>-1</accumulative-max-size>
activemq.management
<accumulative-max-size>0</accumulative-max-size> <!-- unbounded? -->
```
What would be a bit odd is the following:
```
foo.#
<accumulative-max-size>-1</accumulative-max-size>
bar.#
<accumulative-max-size>-1</accumulative-max-size>
```
Perhaps `-1` should only be allowed once, alternatively only on "#"?
> Allow for management messages to pass the global-max-size limit
> ---------------------------------------------------------------
>
> Key: ARTEMIS-1710
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1710
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Ulf Lilleengen
> Assignee: Francesco Nigro
> Priority: Major
>
> Use case: global-max-size is set to some limit to prevent the broker from
> falling over. The broker is configured with N queues which are all blocked by
> this limit.
> If this limit is reached, however, it is not possible to perform management
> operations on the broker, so you're stuck.
>
> It should be possible to have an address like 'activemq.management' bypass
> this limit so that a broker can be recovered when the global-max-size is
> reached.
>
> To work around the problem, an external component needs to ensure that all
> addresses created have a max-size-bytes set so that worst case, there is some
> room left for 'activemq.management' address. In this case the broker
> configuration needs to be known by the component creating addresses which is
> impractical and it feels like this problem would be easier to solve inside
> the broker.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
