[
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 bennetelli opened a pull request:
https://github.com/apache/activemq-artemis/pull/1281
ARTEMIS-1147 Update Hacking Guide Documentation: IDE Integration
the IntelliJ import wizard doesn't contain a sentence like:"Select "Import
from existing model". This should be changed to "import project from external
model" to be conform and the IntelliJ IDEA version should be updated, too.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bennetelli/activemq-artemis
ARTEMIS-1174_Update_Hacking_Guide
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1281.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1281
----
commit 3153d50395085890a9d7108171efc3c1345376cb
Author: Bennet Schulz <m...@bennet-schulz.de>
Date: 2017-05-18T14:04:46Z
ARTEMIS-1147 Update Hacking Guide Documentation: IDE Integration
the IntelliJ import wizard doesn't contain a sentence like:"Select "Import
from existing model". This should be changed to "import project from external
model" to be conform and the IntelliJ IDEA version should be updated, too.
----
)
> 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)
