opentracing-contrib / opentracing-contrib/java-spring-cloud
java.lang.NoSuchMethodError: 'io.opentracing.Scope io.opentracing.Tracer$SpanBuilder.startActive(boolean)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 399
- Forks
- 143
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 22
Description
Hi, i found problem, my dependency tree is:
+--- io.opentracing.contrib:opentracing-spring-jaeger-cloud-starter:3.1.1
| | +--- io.opentracing.contrib:opentracing-spring-jaeger-starter:3.1.1 (*)
| | --- io.opentracing.contrib:opentracing-spring-cloud-starter:0.5.0
| | +--- io.opentracing.contrib:opentracing-spring-rabbitmq-starter:2.0.5
| | | --- io.opentracing.contrib:opentracing-spring-rabbitmq:2.0.5
in pom of spring-cloud-starter:0.5.0 no version param for opentracing-spring-rabbitmq-starter.

In my project i see error in runtime:
[m java.lang.NoSuchMethodError: 'io.opentracing.Scope io.opentracing.Tracer$SpanBuilder.startActive(boolean)'
at io.opentracing.contrib.spring.rabbitmq.RabbitMqTracingUtils.buildReceiveSpan(RabbitMqTracingUtils.java:45) ~[opentracing-spring-rabbitmq-2.0.5.jar!/:?]
May be need to fix used version of starters in pom spring-cloud-starter:0.5.0. May be this usie help people to find this version compability problem
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the spring-cloud-starter:0.5.0 pom and the dependency tree, then trace the failure to RabbitMqTracingUtils.java:45. Reproduce the runtime NoSuchMethodError and verify completion by confirming a compatible resolved starter set and successful startup without that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, rabbitmq, spring, spring-boot
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100