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

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

As [the management 
documentation|http://activemq.apache.org/artemis/docs/1.3.0/management.html] 
notes, you can use the {{listRemoteAddresses}} and 
{{closeConnectionsForAddress}} on the {{ActiveMQServerControl}} to see who is 
connected and close a client connection respectively.

To get more details about who is connected can use {{listConnectionsAsJSON}} on 
{{JMSServerControl}}.  That operation will give you the following details:
* the ID of the connection
* IP address of the client
* time the connection was created
* clientID (relevant for some JMS subscribers)
* username for the connection

There are also a handful of other operations to close connections available on 
{{ActiveMQServerControl}}, e.g.:
* {{closeConnectionsForAddress}} - Closes all the connections for the given IP 
address
* {{closeConsumerConnectionsForAddress}} - Closes all the consumer connections 
for the given messaging address (i.e. _not_ IP address)
* {{closeConnectionsForUser}} - Closes all the connections for sessions with 
the given user name

The {{TopicControl}} and {{QueueControl}} MBeans have various operations to get 
details on subscribers/consumers.

Let me know if you can't do what you need with what is available or if an 
operation should return additional data.  Please be specific.

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

Reply via email to