OpenTracingTracer does not activate the span it creates in onExchangeBegin (i.e. does not invoke tracer.activateSpan). Whenever there is processor invoked down the route, and this processor code is instrumented for OpenTracing (for instance, JDBC calls via opentracing-contrib/java-spring-cloud), the newly created spans are not aware about a trace being active and start a new trace. This leads to all such spans being detached from the route trace. It is a major issue for Camel routes observability via OpenTracing.