Jonas Kunz

I might be a little late to the party, but I started investigating things from the Java side yesterday. I'm trying the "easy path" as a starter as well: Use...

Hi @fr19k , We have another user with the same crash: Both crashes occur due to java.util logging reformatting on the same `System.identityHashCode` invocation. One thing I noticed is that...

I think it should be `java.util.logging.LogManager`, though not 100% sure here. That class has a protected constructor, so we might need to create a subclass to reset it. Alternatively you...

Based on [this SO thread](https://stackoverflow.com/questions/49299649/how-to-configure-log4j2-with-tomcat-8-5-15) it looks like you need to provide the full arguments for the `LOGGING_MANAGER` env variable: `LOGGING_MANAGER="-Djava.util.logging.manager=java.util.logging.LogManager"` If that doesn't work, I think we can also...

Are you running on Java 17+? There have been other similar crashes, like #3521 . We have been in contact with Oracle and managed to reproduce the issue with them,...

We are hoping for the JVM bug to be fixed soon. When that happens we'll remove the option from the agent again, that's why we are not planning to have...

Hi @dbalijapalli0264 , those two exceptions should also have stacktraces in addition to the exception messages. Could you please provide the stacktraces?

Are you using [`Transaction.setName`](https://www.elastic.co/guide/en/apm/agent/java/current/public-api.html#api-set-name) anywhere in you code? The shown error indicates a race condition: * The transaction name is internally stored in a `StringBuilder` * When the transaction ends,...

Hi @candrews, thanks for implementing this, looks definitely useful and we'd like to merge it! However, before doing so we'd like to have an integration test actually starting the APM...

Hi @kelunik, In general we are not planning on extending the public API further, because we want to go with the OpenTelemetry-API as preferred option. We of course will continue...