You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (JIRA)" <ji...@apache.org> on 2017/05/05 14:37:04 UTC
[jira] [Created] (ARTEMIS-1147) Artemis ServerPlugin support for
Broker resource limits reached or exceeded
Matt Pavlovich created ARTEMIS-1147:
---------------------------------------
Summary: 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)