I’m +1 to this. The OTHER big problem with the current JMX stats is that they are poorly implemented as a gigantic synchronized block which then has a bunch of internal synchronized blocks. In some of the load testing I’ve done when using a single route with a lot of threads, I’ve seen a lot of threads blocked on the stats updating. It’s been on my todo list forever to update the stats to use Atomic types or something to remove or reduce the synchronized block, but it’s not a high priority as the simple workaround is to turn off the JMX stats.
Dan On Feb 10, 2014, at 4:14 AM, Claus Ibsen <[email protected]> wrote: > Hi > > Background > http://camel.apache.org/camel-jmx > > In Camel we have a load statistics in JMX that calculates a "load" per > 1, 5, and 15 minutes - which is similar to the concept on unix such as > the top command (load avg) > > Though to do this we have 1 background thread that once per second > calculates the load. That dont matter if you have 1 camel in a JVM. > > But some users have many WARs deployed etc and thus have maybe 30 of > these threads. > > Just wonder if we should switch the default to be turned off, people > can easily turn the stats on, accordingly to the docs in the link > above. > > Any thoughts? > > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: [email protected] > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > Make your Camel applications look hawt, try: http://hawt.io -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
