Stuart McCulloch

Hi @bvoelz19 - in general we don't recommend attaching two tracing `javaagent`s that will both inject advice into the same classes. This is because the injected advice might interact in...

Also is it possible to attach a more complete example which can be unzipped and run?

Hi @cjayacha - `dd-trace-java` uses a fork of `okhttp` which includes a fix for that CVE: * https://github.com/DataDog/dd-trace-java/blob/master/gradle/libs.versions.toml#L46 * https://github.com/DataDog/okhttp/pull/1 it also uses a fork of `okio` which includes a...

Hi @RedVortex - could you open a [support ticket](https://help.datadoghq.com/) and attach the full hs_err file as well as the core dump - thanks!

@RedVortex also if you can recreate this in a staging environment, it would be useful to find out if any of these settings help: ``` DD_CODE_ORIGIN_FOR_SPANS_ENABLED=false DD_UNSAFE_CLASS_INJECTION=true DD_VISITOR_CLASS_PARSING=true ``` Each...

Hi @RedVortex - understood, from the data available at the moment the suggested workarounds would be to either revert to v1.55.0 or turn off the code-origin feature in v1.56.0 with:...

Hi @RedVortex we just released [v1.56.1](https://github.com/DataDog/dd-trace-java/releases/tag/v1.56.1) which should address the reported issue.

Hi @Xyaren - currently the `DD_TRACE_HEADER_BAGGAGE` config setting only applies to the non-W3C baggage representation. It doesn't apply to the W3C baggage representation that is surfaced via the OTel API....

FYI, this is where it would be easiest to add such an environment variable: https://github.com/DataDog/dd-trace-java/blob/v1.56.1/dd-java-agent/agent-bootstrap/src/main/java/datadog/trace/bootstrap/Agent.java#L1432 The recommended approach would be to query the environment variable and (if set) pass the...

Hi @yonigibbs - could you attach a buildable example? That would help progress this issue The changes in #7215 improved context propagation for Kotlin coroutines in general, but it's possible...