We have installed the application agent for AppDynamics and modified setenv.sh to initiate it. AppDynamics seems to load fine, but then JIRA's plugins timeout and the entire application fails to load:
2014-06-03 13:48:50,188 localhost-startStop-1 INFO [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [com.onresolve.jira.groovy.groovyrunner...
2014-06-03 13:48:54,376 localhost-startStop-1 INFO [atlassian.jira.startup.DefaultJiraLauncher] Stopping launchers
2014-06-03 13:48:54,393 localhost-startStop-1 INFO [atlassian.plugin.manager.DefaultPluginManager] Shutting down the plugin system
We have checked memory, CPU, disk, port conflicts, and permGen memory (per https://confluence.atlassian.com/display/JIRAKB/JIRA+System+Plugin+Timeout+While+Waiting+for+Plugins+to+Enable). Removing the AppDynamics JAVA_OPTS from setenv.sh allow JIRA to load properly. The problem is obviously related to AppDynamics, but we aren't sure exactly what the conflict is.
Has anybody run into problems like this installing AppDynamics for JIRA?
Confluence and JIRA use the Felix OSGi container. By default, OSGi containers follow a specific model for bootstrap class delegation. Classes that are not specified in the container's CLASSPATH are not delegated to the bootstrap classloader; therefore you must configure the OSGi containers for the App Server Agent classes. The following link shows you how to configure AppDynamics for Felix environments:
Thanks again, adding the following, as you referenced, seems to have done the trick:
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot