ClassNotFoundException when loading resteasy application on Wildfy application server #4368
Assignees
Labels
comp: telemetry
Telemetry
Comments
|
Hi @vallihalldors, the Instrumentation telemetry can be turned off by setting this environment variable or by adding this system property to your JVM command-line Turning it off will remove the |
|
Regarding the You can disable addition of or by adding this system property to your JVM command-line while we investigate ways to workaround this Spring lookup issue on Wildfly. |
|
Thanks @mcculls. I've applied the workaround you suggested and it works fine. |
|
Also seeing similar issues while using the following configuration: Framework: Ratpack It hangs during a Gradle test when a particular dependency is included on the classpath. I haven't figured out what characteristic of the dependency causes it but excluding it entirely also fixes the issue. With the standard DD agent configuration: [dd.trace 2022-12-09 18:26:10:119 -0600] [dd-task-scheduler] WARN datadog.telemetry.dependency.DependencyResolverQueue - unable to detect dependency for URI file:/Users/user/app-web/build/classes/groovy/test/
[dd.trace 2022-12-09 18:26:41:117 -0600] [dd-task-scheduler] WARN datadog.telemetry.dependency.DependencyResolver - Unable to guess nested dependency for uri 'jar:file:/user/.gradle/caches/modules-2/files-2.1/{{dependencyName}}/2.1.3/2feca93ff0fe8b239606a5542fb956b23a53c95c/{{dependencyName}}-2.1.3.jar!/SpockConfig.groovy': '!/' not found
[dd.trace 2022-12-09 18:26:41:117 -0600] [dd-task-scheduler] WARN datadog.telemetry.dependency.DependencyResolverQueue - unable to detect dependency for URI jar:file:/Users/user/.gradle/caches/modules-2/files-2.1/{{dependencyName}}/2.1.3/2feca93ff0fe8b239606a5542fb956b23a53c95c/{{dependencyName}}-2.1.3.jar!/SpockConfig.groovyIt also just hangs indefinitely if I add the following environment variables: DD_CIVISIBILITY_AGENTLESS_ENABLED=true
DD_INSTRUMENTATION_TELEMETRY_ENABLED=false
DD_INTEGRATION_SPRING_PATH_FILTER_ENABLED=false
./gradlew project:check -Pdd-civisibility -iDATADOG TRACER CONFIGURATIONAny suggestions? |
|
The |
|
Closing as the |
|
I still have this warning with version 1.5.0 : After that, Spring boot restarts and runs fine, but the dual booting is a problem. |
|
@pacome2018 this looks unrelated to the original reported issue which was a class-loading issue related to a tracer bean definition, please open a new issue with as much detail as possible from your application logs before Spring-Boot decided to restart. You may want to enable tracer debug to see if that gives you further details. |
|
@mcculls I still get the same error with version 1.10.0. Do I need to apply the following workaround as a permanent solution? |
|
@vallihalldors can you paste the exception you see with 1.10.0? The factory that was added in #4543 should avoid the Could you also enable tracer debug and see if there are any related exceptions (if you need further investigation of the debug log then you can send it via your support contact) |
|
@mcculls hope this helps: |
|
@vallihalldors thanks - I dug into the We'll need to add specific instrumentation for |
|
Hi @vallihalldors - I've updated the Until then it is also available in this snapshot of the Java tracer: https://oss.sonatype.org/content/repositories/snapshots/com/datadoghq/dd-java-agent/1.11.0-SNAPSHOT/dd-java-agent-1.11.0-20230320.182318-87.jar |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have an issue after upgrading to version 1.1.x (1.1.4). During startup of a service running on Wildfly version 26.1.2.Final when loading RESTEasy application (RESTEasy version 4.7.4.Final) that uses Spring (version 5.3.20) to load the context we get a ClassNotFoundException on datadog.trace.instrumentation.springweb.OrderedServletPathRequestFilter:
I was also wondering if there is a way to get rid of those warnings from the DependencyResolver since we have a lot of those?
The text was updated successfully, but these errors were encountered: