[
https://issues.apache.org/jira/browse/ARTEMIS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389620#comment-15389620
]
Justin Bertram commented on ARTEMIS-587:
----------------------------------------
Stomp does use JMS destinations currently, but Stomp connections don't
originate from the JMS client and are therefore not considered JMS connections
which is what {{JMSServerControl}} essentially deals with.
> 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)
