On Fri, Oct 17, 2014 at 6:39 PM, BlackTie <jts...@hotmail.com> wrote: > I am using hawtio as a standalone WAR, and did some research about accessing > jolokia through hawtio. Browsing through the info that jolokia retrieves > from JMX, not all the processors are listed. I added the maxObjects query > param (with a value of 5000, which is higher than the number of beans we > have) and still, not all the processors are listed. Coupled with the fact > that if you set maxObjects lower than the max number of processor objects > that are available to be retrieved, the json returned contains "[Object > limit exceeded]" after it hits the number specified in maxObjects. >
I logged a ticket at hawtio to take a look at if we can optimize this or have some initial load that has no limitations https://github.com/hawtio/hawtio/issues/1698 > Not only are some of the mbeans missing, but for some routes that actually > did display statistics, after a while the statistics for some processors > stop being shown on the profiling tab in Hawtio. The statistics for the > processors that have stopped being shown in Hawtio are still in JMX. Weird! > > I have used jconsole to look at the list of processors, and it looks the > same as the list through hawtio. Some of the processors are missing, even > on a fresh startup of my webapp. > That is odd if jconsole does not also list all the processors, then hawtio can neither find them. You can enable DEBUG logging for org.apache.camel.management. And it should log when it enlists a processor as MBean. Maybe you can see if the missing processors at least is DEBUG logged. Also mind that if you turn on the option onlyRegisterProcessorWithCustomId=true then only processors with a custom id is enlisted. But that is not enabled by default. > It sounds like I am running into two separate problems: > * Some processors are never showing up in JMX at all > * Hawtio stops showing statistics at some point for some processors, but I > can still look at the statistics through JMX > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Not-all-processors-are-listed-in-JMX-preventing-detailed-route-statistics-profiling-tp5757634p5757739.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
