[
https://issues.apache.org/jira/browse/ARTEMIS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392512#comment-15392512
]
ASF GitHub Bot commented on ARTEMIS-587:
----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/662
ARTEMIS-587 add more JSON JMX mgmt methods to core
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-587
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/662.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 #662
----
commit cc540302ae5fbfe9313806dc2e28421bc4b118f3
Author: jbertram <[email protected]>
Date: 2016-07-22T22:37:27Z
ARTEMIS-587 add more JSON JMX mgmt methods to core
----
> Expose connection and subscription information via JMX
> ------------------------------------------------------
>
> Key: ARTEMIS-587
> URL: https://issues.apache.org/jira/browse/ARTEMIS-587
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Lionel Cons
> Assignee: Justin Bertram
>
> ActiveMQ 5.x does expose connection information via JMX.
> This allows to find out who is connected to a broker but also who consumes
> from which queue or topic. One can also delete connections, for instance to
> kill a stuck consumer.
> I did not find the equivalent functionality in Artemis.
> Could Artemis be improved to expose in JMX the list of connections (with
> remote address, port number, credential used to authenticate, list of
> subscriptions...) as well as (at least) an operation to force the end of a
> given connection?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
