Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-28 Thread Claus Ibsen
e all the processors > get registered in the debug logging of DefaultManagementAgent. If I rerun > with the route actually being transacted, those processors don't show up in > the logging. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-28 Thread BlackTie
d see all the processors get registered in the debug logging of DefaultManagementAgent. If I rerun with the route actually being transacted, those processors don't show up in the logging. -- View this message in context: http://camel.465427.n5.nabble.com/Not-all-processors-are-lis

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-28 Thread Charles Moulliard
nsole). > > I've looked at the configuration of Camel and JMS and nothing looks out of > the ordinary to me, but there seems to be something with transacted routes > that prevent those processors from being registered. > > > > > -- > View this message in context

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-27 Thread BlackTie
s to be something with transacted routes that prevent those processors from being registered. -- View this message in context: http://camel.465427.n5.nabble.com/Not-all-processors-are-listed-in-JMX-preventing-detailed-route-statistics-profiling-tp5757634p5758143.html Sent from the Camel - User

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-27 Thread Claus Ibsen
t; > > -- > 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 ---

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-24 Thread BlackTie
recorded for the processors of those routes in JMX. Charles Moulliard-2 wrote > Do you have a use case that we could use to reproduce the issue ? -- View this message in context: http://camel.465427.n5.nabble.com/Not-all-processors-are-listed-in-JMX-preventing-detailed-route-statistics-prof

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-23 Thread Charles Moulliard
; > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Not-all-processors-are-listed-in-JMX-preventing-detailed-route-statistics-profiling-tp5757634p5757959.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-23 Thread BlackTie
5.10.0 * ActiveMQ Camel component's JMS config has transacted=true -- View this message in context: http://camel.465427.n5.nabble.com/Not-all-processors-are-listed-in-JMX-preventing-detailed-route-statistics-profiling-tp5757634p5757959.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-20 Thread Charles Moulliard
es use JMS transactions so that we don't drop in-flight messages. >> >> I just noticed while looking in hawtio at the mbeans for Camel that there >> are no transacted processors listed. >> >> >> >> -- >> View this message in context: >> http:/

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-20 Thread Charles Moulliard
ansactions so that we don't drop in-flight messages. > > I just noticed while looking in hawtio at the mbeans for Camel that there > are no transacted processors listed. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Not-all-processors-

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-20 Thread BlackTie
om/Not-all-processors-are-listed-in-JMX-preventing-detailed-route-statistics-profiling-tp5757634p5757820.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-19 Thread Willem Jiang
> > -- > 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. >

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-17 Thread BlackTie
wtio 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

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-16 Thread Andrew Thorburn
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. >

Not all processors are listed in JMX, preventing detailed route statistics/profiling

2014-10-16 Thread BlackTie
gent 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