Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 18 May 2017 15:08:04 +0000 (UTC)
From: "Justin Bertram (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.13069471.1493995011000.241935.1495120084258@Atlassian.JIRA>
In-Reply-To: <JIRA.13069471.1493995011000@Atlassian.JIRA>
References: <JIRA.13069471.1493995011000@Atlassian.JIRA> <JIRA.13069471.1493995011293@jira-lw-us.apache.org>
Subject: [jira] [Issue Comment Deleted] (ARTEMIS-1147) Artemis ServerPlugin
 support for Broker resource limits reached or exceeded
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 18 May 2017 15:08:08 -0000


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

Justin Bertram updated ARTEMIS-1147:
------------------------------------
    Comment: was deleted

(was: Github user clebertsuconic commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1281
  
    don't know.. perhaps you did on a wrong branch?
)

> Artemis ServerPlugin support for Broker resource limits reached or exceeded
> ---------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1147
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1147
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Matt Pavlovich
>
> The ArtemisServerPlugin should have API hooks for tying into broker resource limit events such as, producer flow control, storage full, fast producer, slow consumer, message size, connection count, etc
> The 5.x tree had these as separate operations. It may make more sense to have it be one operation (or group operations around broker object types) to allow for non-API changing extensibility in the future.
> Key features: 
>   * FastProducer -- needs to have access to the connectionId, clientId, sessionId and destination(s) involved
>   * SlowConsumer -- needs to have access to the connectionId, clientId, sessionId and destination(s) involved
>   * Connection count limit exceeded -- needs to have access to the connectionId, clientId, sessionId and requested destination
>   * StorageLimit reached
>   * MemoryLimit reached
>   * Message size limit exceeded -- needs to have access to the connectionId, clientId, sessionId and requested destination


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)