Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of nzipsi@gmail.com designates
 209.85.213.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1413492094450-5757634.post@n5.nabble.com>
References: <1413492094450-5757634.post@n5.nabble.com>
Date: Fri, 17 Oct 2014 17:12:23 +1100
Message-ID: 
 <CAJUvgM6J3W0UAr+KxtMeQuc0w_dE+b1MsBJog8OyAp_x2JTQVg@mail.gmail.com>
Subject: Re: Not all processors are listed in JMX,
 preventing detailed route statistics/profiling
From: Andrew Thorburn <nzipsi@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=047d7b3a97ea95574f0505983f27

--047d7b3a97ea95574f0505983f27
Content-Type: text/plain; charset=UTF-8

I've seen issues like this in HawtIO, and it's actually a Jolokia issue.
Basically, Jolokia will only fetch the first N elements (unsorted, I
believe) from the server, and if your MBean isn't one of those N, then...
bugger?

The solution is to go into HawtIO / Preferences / Jolokia, and change Max
Collection Size from 500 (the default) up to a larger number. I went to
5000, and all of a sudden all my routes appeared in the Camel console, and
in the JMX tab. This will have an impact on browser performance, but I'm
not sure there's much that can be done, apart from raising a feature
request with Jolokia / HawtIO-Camel to fetch only a subset of available
MBeans, rather than fetching them all and filtering on the client-side.

Now, if you're looking at the JMX info through a different source (not
HawtIO/Jolokia) and still not seeing them all, then this probably won't
help much.

- Andrew

On Fri, Oct 17, 2014 at 7:41 AM, BlackTie <jtstor@hotmail.com> wrote:

> I have a webapp using Camel (v2.13.2) about to go into production, at the
> point of trying to tune things for performance.  I'm having an issue with
> getting detail statistics for some routes, though.  I'm using Hawtio 1.2,
> and for some routes, Hawtio is displaying the statistics for each processor
> in the route, and others it only shows the statistics at the route level.
> I
> checked JMX with jconsole and noticed that, for the routes that don't show
> specifics for the processors, the processors in those routes are not listed
> under the processors section in JMX.  Some routes with this problem are
> complex, others are fairly simple.
>
> Any ideas what would cause some to/choice/multicast/etc processors from not
> being listed in JMX at all?  Without the statistics, it makes it very
> difficult to figure out where things are slowing down when the system is
> under heavy load.
>
> The jmxAgent is enabled for the camel context, with statisticsLevel set to
> All.
>
> Thanks for any help you can provide on this problem!
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Not-all-processors-are-listed-in-JMX-preventing-detailed-route-statistics-profiling-tp5757634.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

--047d7b3a97ea95574f0505983f27--