We have a couple of Java app services (deployed as jars) on azure. The jar's are started via the IIS web.config file which starts java.exe as an httpPlatform process.
We have to stick to this troubled mechanism which involves manually configuring the OneAgent JVM arg as follows:
java.exe ... -agentpath:\home\SiteExtensions\Dynatrace.Agent\184.108.40.20610609-185653\agent\lib64\oneagentloader.dll=server=https://***.live.dynatrace.com:443,tenant=***,tenanttoken=***,loglevelcon=info -Xshare:off
(where *** is our dynatrace server)
The above was all working fine albeit clunky with OneAgent extension version 1.217.X, however our new java app service has a higher OneAgent extension installed of 1.231.X, so replacing 1.217.X with 1.231.X in the above didn't work. I had to change to the below instead:
java.exe ... -agentpath:\home\SiteExtensions\Dynatrace.Agent\220.127.116.1120112-085307\agent\bin\18.104.22.16820112-085307\windows-x86-64\oneagentloader.dll=server=https://***.live.dynatrace.com:443,tenant=***,tenanttoken=*** -Xshare:off
Since doing this we now get monitoring of our java app service BUT we're seeing these exceptions in the logs which we weren't before:
Handler dispatch failed; nested exception is java.lang.NoClassDefFoundError: com/dynatrace/agent/introspection/http/ApacheHttpIntrospectionWrapper
Can anyone suggest what I might be doing wrong? We're using Java 11 / Spring Boot 2.1.X
@lv25804 were you able to get to a rootcause/resolution to your log exceptions? Is the issue still persistent?