Hi,
Whne the AppDynamics is connected with the Jira standalone the Application fails to comeup, whereas the same set-up comes up fine when not connected with the Agent.
The following is the console out when connected with the agent:
---------------------------------------------------------------------------------------------------
2012-03-15 23:17:05,034 main INFO [atlassian.jira.startup.JiraStartupLogger]
********************************************************************************
JIRA 4.4.4 build: 664 started. You can now access JIRA through your web browser.
********************************************************************************
2012-03-15 23:17:05,094 main FATAL [atlassian.jira.startup.JiraStartupLogger]
********************************************************************************************************************************************************************************************************
The following plugins are required by JIRA, but have not been started: Gadget Directory Plugin (com.atlassian.gadgets.directory), Atlassian JIRA - Plugins - Project Config Plugin (com.atlassian.jira.jira-project-config-plugin), Atlassian OAuth Admin Plugin (com.atlassian.oauth.admin), Embedded Gadgets Plugin (com.atlassian.gadgets.embedded), Atlassian JIRA - Plugins - Shared Application Access Layer (SAL) Plugin (com.atlassian.sal.jira), Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard), Atlassian JIRA - Plugins - Look And Feel Logo Upload Plugin (com.atlassian.jira.lookandfeel), Atlassian JIRA - Plugins - OAuth Consumer SPI Plugin (com.atlassian.jira.oauth.consumer), Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets), Atlassian REST - Module Types (com.atlassian.plugins.rest.atlassian-rest-module), Atlassian JIRA - Plugins - OAuth Service Provider SPI Plugin (com.atlassian.jira.oauth.serviceprovider), Gadget Spec Publisher Plugin (com.atlassian.gadgets.publisher), Atlassian JIRA - Plugins - REST Plugin (com.atlassian.jira.rest), Atlassian OAuth Service Provider Plugin (com.atlassian.oauth.serviceprovider), Atlassian OAuth Consumer Plugin (com.atlassian.oauth.consumer), Opensocial Plugin (com.atlassian.gadgets.opensocial)
********************************************************************************************************************************************************************************************************
2012-03-15 23:17:05,097 main FATAL [atlassian.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked.
Please follow steps mentioned as per http://litedocs.appdynamics.com/display/ADLite2/OSGi+Infrastructure documentation .
Regards,
Arpit Patel
Hi,
Is it the same error every time, i.e. "JIRA startup failed, JIRA has been locked"? If so it sounds like you're hitting one of the locking reasons documented at http://confluence.atlassian.com/display/JIRAKB/JIRA+is+Locked
Looking at the agent installation instructions for AppDynamics the agent runs in the same JVM instance that the app server uses so you could be hitting a PermGen memory error. Could you try increasing the amount of PermGen allocated to the JVM (http://confluence.atlassian.com/display/JIRAKB/JIRA+Crashes+Due+to+'java.lang.OutOfMemoryError+PermGen+Space+Error)and see if that fixes things?
Andrew.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.