We are using JIRA v4.3.4 with a v1 JaM v6.2 plugin and have been using them together successfully for over a year.
JIRA was shutdown and restarted recently where we then received the following message:
"JIRA Startup Failed You cannot access JIRA at present. Look at the table below to identify the reasons
Description "Error occured while starting component com.atlassian.jira.event.DefaultListenerManager'."
The catalina.out errors indicated it was the mercury_kit-6.2-GA.jar file. We removed the jar file from atlassian-jira/WEB-INF/lib and JIRA restarted without error and all other plugins worked fine. When shutdown occured, Tomcat closed successfully.
What could be causing this error with the plugin and preventing JIRA from starting? Could this issue be occuring due to a locked file or stuck process that needs to be forced closed? Are there specific locations we haven't found yet that could possibly have corrupt files or processes that are for the JaM plugin and preventing JIRA from staring?
I have contacted the Go2Group but have recieved no answer resolving this issue.
Any assistance is greatly appreciated.
Thank you and have a great day.
Have you tried the following (with plugin installed):
This couses Jira to redeploy all plugins. Not sure if it will fix the problem, but worth the try.
It started as any story starts, on a normal, rainy day. Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs