The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Installing AppDynamics Prevents Plugins from Loading

JasonT
June 2, 2014

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

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Pranta Das
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 3, 2014

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

JasonT
June 4, 2014

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

JasonT
June 4, 2014

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.*

0 votes
JasonT
June 2, 2014

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

Thanks