[
https://issues.apache.org/jira/browse/ARTEMIS-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667828#comment-16667828
]
ASF GitHub Bot commented on ARTEMIS-1710:
-----------------------------------------
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2401
> Surely this would be better handled with simply setting better values per
address.
I could be wrong (and @mtaylor or @clebertsuconic can help me to understand
the conditions I have found in the code), but it seems to me that the
global-max-size can never be surpassed, regardless any configuration you'll set
for a maching address.
@lulf in the referenced issue has explained it very clearly: if you desire
to have a global-max-size to be shared between all the addresses, but you need
management messages to not being influenced by it, it doesn't seem possible
with the current broker configuration.
By default this option is disabled ie management addresses behave like we
are always used to see.
> Or at least implementing a two tier max, keeping the existing
global-max-size as behaviour today (so users dont get a change in expectation),
but implementing a secondary value thats global-non-management-max-size that
could be a catch all at a level below.
That's a good point: I like the idea of a `global-non-management-max-size`
(while leaving `global-max-size` unbounded): what makes me not 100% sure of it
is that to satisfy that same requirement it will introduce a whole new
feature, probably bigger. Let me think about it and hear the others opinions on
it :+1:
> 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)
