[
https://issues.apache.org/jira/browse/ARTEMIS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387379#comment-15387379
]
Lionel Cons commented on ARTEMIS-587:
-------------------------------------
Digging more, it seems that the problem comes from a lack of sessions.
In my test, I have a single STOMP client connected but doing nothing.
In JMX, I can see a single remote address via {{listRemoteAddresses}} and a
single connect ID via {{listConnectionIDs}}. So far, so good.
However, {{listConnectionsAsJSON}} returns an empty array. So does
{{listSessions}} and {{listSessionsAsJSON}} when given the connection ID
returned by {{listConnectionIDs}}.
I don't know how the concept of sessions apply to STOMP.
> 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)
