Jax RS Tracing broken
See original GitHub issueWe upgraded our java agent to version 0.12.0
and noticed that we no longer received any traces for servlet.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 to 0.11.0
and started receiving the servlet.request
traces again. We are running jetty version 9.3.6.v20151106
and jersey version 2.22.1
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0 - Oracle
Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0 ... I set the property, but still get an 500 without any trace in...
Read more >Can I log when my JAX-RS application can't send its response ...
Try using a servlet filter to trap exceptions when the socket is closed prematurely. Make sure it's first in your web.xml. import java.io....
Read more >JaxRS injection broken at REL_2.3-20141028230028+0000 ...
When upgrading between these two gradle versions JAX RS injections break (in a junit test case) with the following stack trace:.
Read more >What to do when JAX-RS cannot find it's Providers aka My ...
One of the reasons why I wrote this article is my, rather unusual, encounter with a missing message body writer in a Jersey...
Read more >Chapter 23. Monitoring and Diagnostics - GitHub Pages
This facility may provide vital information when troubleshooting your misbehaving Jersey or JAX-RS application. When enabled, Jersey tracing facility collects ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Opened ticket #160129 for this issue.
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.