camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bengt Rodehav <>
Subject Re: Enabling tracing in production
Date Sat, 30 Oct 2010 08:49:31 GMT
I have a similar situation but I'm not using Spring - I use Java DSL and

I have my own tracer that I can publish as an OSGi service using iPOJO. I
want to accomplish the following. My other services shall have optional
service dependencies to my tracer. This means that if my custom tracer is
available then it should be used, otherwise the default tracer should be

However, just publishing my tracer and requiring it in my other components
does not automatically cause Camel to use it. I have to to the following:



In other words I explicitly set my tracer to be used, I then disable tracing
since the first line seems to automatically enable tracing. I then use JMX
to enable/disable tracing. I was hoping the above two lines were unnecessary
and that merely the existence of a tracer should cause Camel to use it. Is
that a Spring specific functionality? I was hoping that any way that an OSGi
service was published/consumed would work?


2010/10/30 Richard Kettelerij <>

> You don't have to add a Tracer to your Spring context yourself. Camel adds
> one automatically if you have a CamelContext declared in Spring. Also your
> don't have to do anything with the "trace" option in your Spring context.
> I find that the easiest way to enable/disable tracing in production is
> through JMX. Just navigate to the CamelContext MBean and modify the
> "tracing" attribute. Additionally you can determine what should be traced
> by
> modifying a few options in the Tracer MBean.
> -----
> Richard Kettelerij,
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message