[
https://issues.apache.org/jira/browse/ARTEMIS-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673373#comment-16673373
]
ASF GitHub Bot commented on ARTEMIS-1710:
-----------------------------------------
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/2401
@franz1981 / @michaelandrepearce : Management messages exist to manage the
broker. they are passed right into QueueController and are not queued.
Hence they should not be managed by blocking / paging or anything.
They should just be consumed right away, and not parsed by PagingManager..
never.
I actually thought this was the case..
This could block you out.
Say you need to drop a queue because the broker memory is off limits. if
your only option is to use management messages, you're locked out of our own
broker.
Hence... management messages shouldn't be blocked or paged. they should
just be consumed right away.
i consider this a bug. .and it should be fixed without adding any
configuration.
if (isManagement) maxSize = -1;... don't use any blocking / paging / fail!
> Allow for management messages to exceed 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)
