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

ASF GitHub Bot commented on ARTEMIS-587:
----------------------------------------

Github user jbertram commented on a diff in the pull request:

    https://github.com/apache/activemq-artemis/pull/662#discussion_r72130781
  
    --- Diff: 
artemis-server/src/main/java/org/apache/activemq/artemis/core/management/impl/ActiveMQServerControlImpl.java
 ---
    @@ -1360,6 +1359,130 @@ public String listProducersInfoAsJSON() throws 
Exception {
        }
     
        @Override
    +   public String listConnectionsAsJSON() throws Exception {
    +      checkStarted();
    +
    +      clearIO();
    +
    +      try {
    +         JSONArray array = new JSONArray();
    +
    +         Set<RemotingConnection> connections = 
server.getRemotingService().getConnections();
    +
    +         for (RemotingConnection connection : connections) {
    --- End diff --
    
    That's fine with me.  


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

Reply via email to