-
Notifications
You must be signed in to change notification settings - Fork 782
Unclosed Span in ribbon client #240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Milestone
Comments
Josh can you provide these steps to reproduce it?
|
I think I did it. If I use Feign and Ribbon/Hystrix and don't define a server list I can break the ribbon sample in Sleuth. |
dsyer
pushed a commit
that referenced
this issue
Mar 31, 2016
Commit 84f4d37 adds a sample that fails (e.g. run it and curl localhost:3383/). |
I have a test that fails and I can fix it, but it won't run in a suite because of some stale state from one of the other tests. Needs more work. |
shivangshah
pushed a commit
to shivangshah/spring-cloud-sleuth
that referenced
this issue
Apr 1, 2016
shivangshah
pushed a commit
to shivangshah/spring-cloud-sleuth
that referenced
this issue
Apr 1, 2016
The retryable case was already covered and tested but if the exception is not retryable, we need to rethrow and clean up the thread state. Fixes spring-cloudgh-240
shivangshah
pushed a commit
to shivangshah/spring-cloud-sleuth
that referenced
this issue
Apr 1, 2016
shivangshah
pushed a commit
to shivangshah/spring-cloud-sleuth
that referenced
this issue
Apr 1, 2016
The retryable case was already covered and tested but if the exception is not retryable, we need to rethrow and clean up the thread state. Fixes spring-cloudgh-240
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This one is hard to reproduce I think, but @joshlong had a sample where there were WARN logs about uncloseable spans from a Ribbon client that couldn't resolve its server. It was using Feign as well.
The text was updated successfully, but these errors were encountered: