-
Notifications
You must be signed in to change notification settings - Fork 286
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
Jax RS Tracing broken #424
Comments
Thanks for the report. Would it be possible to open a support ticket so you can provide some logs and such? |
Opened ticket #160129 for this issue. |
@chouze We are waiting for a response on that ticket. Providing logs, specifically the jvm startup logs with Thanks! |
Hello, sorry for the delay, I've sent in a few minutes of logs. |
@chouze We've made a fair bit of changes since
Thanks! |
Hi @tylerbenson, I just tried with |
@choze, darn. I was hopeful. Is it possible for you to provide a small sample app that reproduces the problem? Can you tell me more about your application environment? Using Spring Boot, OSGi, or some other non-standard classloading setup? |
from my experience, |
Closing as abandoned. We've made significant improvements to the tracer in the past year (and specifically Jax-rs more recently) Please open a new issue if the problem persists with a newer version of the tracer. |
We upgraded our java agent to version
0.12.0
and noticed that we no longer received any traces forservlet.request
in the Datadog APM dashboard. To the best of our knowledge we still received all the traces for all other types. We reverted back down to0.11.0
and started receiving theservlet.request
traces again. We are running jetty version9.3.6.v20151106
and jersey version2.22.1
.The text was updated successfully, but these errors were encountered: