Thanks for the response Peter. We had already setup the first three exclusions you provided, so I added the fourth - still getting the same error.
I'm attaching the log folder for the agent. I purged the old logs and then went through tomcat startup so it should only contain relevant data.
As it turns out, the other 2 servers that I thought were working are not - I had an invalid character in app-agent-config.xml, which meant that it allowed the BillingCenter process to start, but did not start the AppDynamics agent. So I suspect all three servers will have the same issue now (but I can't re-start it to validate, as people are actively testing in that environment right now).
Related to your comment about Guidewire and OSGI - I found some references on the web that implied Guidewire was moving in that direction. Since we recently upgraded BillingCenter to version 9.x, it's very possible that it does use OSGI.
Thanks for you assistance!
... View more
I have seen this referenced in several other posts related to other servers, like JBoss, but nothing that seems to help me.
We have a system called Guidewire BillingCenter, which runs on Tomcat 8. I have 2 servers that have the Java agent applied and are running fine, but one machine gets the exception at startup: java.lang.NoClassDefFoundError: com/singularity/ee/agent/appagent/entrypoint/bciengine/FastMethodInterceptorDelegatorBoot
From what I can tell this is a classpath issue, right? If so, what would allow one server to work fine, while another fails? I have compared both the working and non-working servers as best I can and I can't find any differences that would explain this behavior.
... View more