Hi Yes as I said Camel producers are not enlisted in JMX by Camel. But as its just JMX you could manually enlist it in JMX.
We could start enlisting Camel producers in JMX as we do for consumers during startup. The reason we didnt do that in the past was that we would enlist any Camel producer being created at runtime, and for dynamic EIPs that could potential lead to unlimed number of producers enlisted in JMX causing it to eat the memory or enlist too many producers which you may not want to see, or the producer was a one-time in use only. But today we got logic in camel-core that can only enlist during startup, so we could do that for producers too. I thought there was a ticket about it, but couldn't find it, so I logged a new ticket. https://issues.apache.org/jira/browse/CAMEL-7604 On Wed, Jul 16, 2014 at 10:13 AM, dermoritz <[email protected]> wrote: > I think i identified the "producer" in question. It is the one of the "to" > processors. The problem is that this one seems to completely ignore the > annotations. The processor exposes same attributes and other stuff like all > other "to" processors while my annotated consumer only exposes those stuff i > annotated. > > Probably i got you wrong here. Is there a way to expose special > attributes/operations of a consumer and are we talking only about a problem > with categories used in jconsole (the i probably did something wrong?). Or > is it not possible to expose custom stuff from within a producer? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/How-to-expose-camel-producer-with-jmx-tp5753833p5753902.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
