Since I feel it is necessary in any case, I did a PR to log the location of the classes that agent causes loading and with the ability to disable the checks we do that may raise this problem. You can download this snapshot jar and test it.
With this snapshot, if you set the agent log level to
DEBUG it should print out where it found the
In addition, by adding
-Delastic.apm.enable_class_loading_pre_filtering=false to the agent config you would disable the code that I suspect is related to it and see if this solves the problem. The effect would be longer startup time, but not necessarily very considerable, depending on your app.