Installing AppDynamics Prevents Plugins from Loading

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?

Thanks,

Jason

2 answers

1 accepted

Accepted Answer
0 votes

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:

http://docs.appdynamics.com/display/PRO14S/OSGi+Infrastructure+Configuration#OSGiInfrastructureConfiguration-ToconfigureFelixforJiraorConfluence

Thanks, I will give that a try and let you know.

Thanks again, adding the following, as you referenced, seems to have done the trick:

-Datlassian.org.osgi.framework.bootdelegation=META-INF.services,com.yourkit,com.singularity.*,com.jprofiler,com.jprofiler.*,org.apache.xerces,org.apache.xerces.*,org.apache.xalan,org.apache.xalan.*,sun.*,com.sun.jndi,com.icl.saxon,com.icl.saxon.*,javax.servlet,javax.servlet.*,com.sun.xml.bind.*

I should also note that we increased -Datlassian.plugins.enable.wait to 300 seconds, but plugins were still unable to start.

Thanks

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 16, 2018 in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

74 views 0 3
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you