Open nbverboven-tiendanube opened 1 year ago
This sort of exception has been known to happen when you have two -javaagent
s installed and they both attempt to instrument the same class.
We usually recommend putting Datadog's -javaagent
option first on the command-line, which has helped in a number of cases. Otherwise if there's an easy way to recreate it then we can investigate further.
Hi @mcculls, thanks for answering.
I tried changing the order of the -javaagent
options but it didn’t work. The only way I could get the service to start was to have only one of them.
Unfortunately, the Lightbend plugin requires a paid subscription so I don’t think there’s an easy (or cheap) way to recreate the issue.
An update on this: according to Lightbend, their plugin isn't compatible with newer versions of the Datadog java agent. It's in their backlog but with no defined timeline.
To provide some context, we’re currently migrating part of our observability stack to Datadog. In one of our Scala services, we noted that having Lightbend's Cinnamon sbt plugin together with v1.10.0 of the Datadog java agent causes the application to fail on startup with the following stack trace
Our workaround was to set
-Ddd.trace.classes.exclude=akka.http.scaladsl.HttpExt
(a similar method was described in #4435).Is this the expected behavior?