Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 9 Aug 2012 17:23:19 +0000 (UTC)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: commits@activemq.apache.org
Message-ID: <906465912.2638.1344532999664.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1861139479.5898.1333455505890.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (APLO-179) Remove the list of connections from
 the toplevel REST URI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/APLO-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino resolved APLO-179.
--------------------------------

    Resolution: Fixed

You can also now optionally a a list of connections associated to a connector at via the connector URL.
Fix should show up in the next nightly build.
                
> Remove the list of connections from the toplevel REST URI
> ---------------------------------------------------------
>
>                 Key: APLO-179
>                 URL: https://issues.apache.org/jira/browse/APLO-179
>             Project: ActiveMQ Apollo
>          Issue Type: Improvement
>          Components: apollo-broker, apollo-web
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.5
>
>
> The toplevel REST URI to get broker information (http://localhost:61680/broker) currently contains the list of all established connections.
> This may look handy but it brings problems on a broker with thousands of connections: the data takes several seconds to be generated and unnecessary information gets reported. This is problematic for monitoring tools frequently accessing this URI to get high-level information such as JVM metrics.
> I would suggest to use a dedicated URI to list all the connections and only report the count on the toplevel URI.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira