activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-587) Expose connection and subscription information via JMX
Date Thu, 21 Jul 2016 22:18:20 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388524#comment-15388524
] 

Justin Bertram commented on ARTEMIS-587:
----------------------------------------

Since your use-case involves Stomp (which wasn't clear in the description) then using anything
from {{JMSServerControl}} will be fruitless. We'll need to implement more connection and session
related info-management operations on {{ActiveMQServerControl}}.

> 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)

Mime
View raw message