You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Until now we seem to have avoided OpenTracing API incompatibilities between 0.31.0 (used by Quarkus) & 0.33.0 (used by Camel). The Camel OpenTracingTracer now invokes a method that is not present in 0.31.0, hence we see:
[INFO] Running org.apache.camel.quarkus.component.opentracing.it.OpenTracingTest
2020-07-22 09:34:37,146 INFO [org.apa.cam.qua.cor.CamelBootstrapRecorder] (main) bootstrap runtime: org.apache.camel.quarkus.main.CamelMainRuntime
2020-07-22 09:34:37,184 INFO [org.apa.cam.mai.BaseMainSupport] (main) Auto-configuration summary:
2020-07-22 09:34:37,185 INFO [org.apa.cam.mai.BaseMainSupport] (main) camel.context.name=quarkus-camel-example
2020-07-22 09:34:37,205 INFO [org.apa.cam.qua.mai.CamelMainRoutesCollector] (main) Loading additional Camel XML route templates from: classpath:camel-template/*.xml
2020-07-22 09:34:37,226 ERROR [io.qua.application] (main) Failed to start application: java.lang.NoSuchMethodError: 'boolean io.opentracing.util.GlobalTracer.registerIfAbsent(io.opentracing.Tracer)'
at org.apache.camel.opentracing.OpenTracingTracer.registerGlobalTracer(OpenTracingTracer.java:234)
at org.apache.camel.opentracing.OpenTracingTracer.doInit(OpenTracingTracer.java:228)
at org.apache.camel.support.service.BaseService.init(BaseService.java:83)
at org.apache.camel.support.service.ServiceHelper.initService(ServiceHelper.java:55)
at org.apache.camel.impl.engine.AbstractCamelContext.internalAddService(AbstractCamelContext.java:1485)
at org.apache.camel.impl.engine.AbstractCamelContext.addService(AbstractCamelContext.java:1403)
at org.apache.camel.opentracing.OpenTracingTracer.init(OpenTracingTracer.java:126)
at org.apache.camel.opentracing.OpenTracingTracer.createRoutePolicy(OpenTracingTracer.java:114)
AFAIK - Quarkus will not move to OpenTracing 0.33.x until MicroProfile OpenTracing is upgraded to 2.0.
The text was updated successfully, but these errors were encountered:
ppalaga
changed the title
OpenTracing integration test fails with Camel 3.5.0-SNAPSHOT
[Camel 3.5] OpenTracing integration test fails with Camel 3.5.0-SNAPSHOT
Aug 10, 2020
Until now we seem to have avoided OpenTracing API incompatibilities between 0.31.0 (used by Quarkus) & 0.33.0 (used by Camel). The Camel
OpenTracingTracer
now invokes a method that is not present in 0.31.0, hence we see:AFAIK - Quarkus will not move to OpenTracing 0.33.x until MicroProfile OpenTracing is upgraded to 2.0.
The text was updated successfully, but these errors were encountered: