confluence 7.13 with Adaptavist Scriptrunner fails to run with apm 20.2

[Stefan Pivoda]

hi,

when Adaptavist Scriptrunner is started on confluence 7.13.0, it runs into the next exception, if it is monitored by APM 20.2 agent. without APM it's working without any issue.

Exception Details:

Location:

com/onresolve/scriptrunner/runner/GenericsHandlingGroovyScriptEngine.<init>([Ljava/net/URL;)V @385: new

Reason:

Type top (current frame, locals[4]) is not assignable to uninitializedThis (stack map, locals[4])

Current Frame:

bci: @30

flags: { flagThisUninit }

locals: { uninitializedThis, '[Ljava/net/URL;', '[Lorg/codehaus/groovy/runtime/callsite/CallSite;' }

stack: { '[Ljava/lang/Object;', uninitializedThis, integer }

Stackmap Frame:

bci: @385

flags: { flagThisUninit }

locals: { uninitializedThis, '[Ljava/net/URL;', '[Lorg/codehaus/groovy/runtime/callsite/CallSite;', top, uninitialize

dThis, 'com/wily/introscope/agent/trace/IMethodTracer' }

stack: { '[Ljava/lang/Object;', uninitializedThis }

do you have please any idea how to fix it?

PS: adding

CATALINA_OPTS="-Datlassian.org.osgi.framework.bootdelegation=com.wily,com.wily.*,sun.*,org.w3c.*,org.xml.sax.*,org.apache.xerces.*,com.sun.org.apache.xalan.*, org.apache.xml,org.apache.xml.*,javax.xml,javax.xml.*,com.sun,com.sun.*org.apache.xalan,org.apache.xalan.*${CATALINA_OPTS}"

CATALINA_OPTS="-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl${CATALINA_OPTS}"

CATALINA_OPTS="-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl${CATALINA_OPTS}"

was tried as well (as it was mentioned for APM 10.7), but in that case tomcat even didnt start because of
Error: Could not find or load main class org.apache.xml,org.apache.xml.*,javax.xml,javax.xml.*,com.sun,com.sun.*org.apache.xalan,org.apache.xalan.*

Caused by: java.lang.ClassNotFoundException: org.apache.xml,org.apache.xml.*,javax.xml,javax.xml.*,com.sun,com.sun.*org.apache.xalan,org.apache.xalan.*
thank you, stefan

[David Lewis]

Hi Stefan,
It looks like there is an attempt to instrument this class, or at least to check it over
com/onresolve/scriptrunner/runner/GenericsHandlingGroovyScriptEngine

I'm not sure what there is in the default instrumentation that would mean this class is instrumented.

It would help to check the AutoProbe log to see if there is an instrumentation attempt. Part of checking the AutoProbe log would be to see what related pbds are instrumented, maybe it's the smart instrumentation that is trying to monitor that component. The class name itself might not show up, it could be a class it inherits from, if any.

If it is smart instrumentation, it would make sense to turn off a few options and also make sure the AutoPersist.pbd is cleared out of the agent's hotdeploy folder, this should help with the scenario.

If you have access to SaaS, it's possible to try the latest agent version and see if that makes a difference, otherwise if you raise a case, we could upload the latest agent.

Beyond that, there is a debug option for the agent to gather data about the class that we would normally raise to engineering, but I can't find the exact property at the moment - the data gathered in that scenario is only useful to engineering.

So basically it feels like the sort of thing we should look more into with support, if the hints above don't help. In any case, we should identify why the agent is hitting an issue there as it can be an agent bug,

Thanks,
David