JIRA Plugin customfield Startup Failed

Question

I have developed a JIRA customfield Plugin, the JAVA sourcecode doesn't show me any Errors.

I am able to install this plugin with all modules and it is running perfectly.

But if i try to restart JIRA Server I get an ERROR in the JIRA log file and the startup Screen looks like this.

error.PNG

The ERROR code in the atlassian-jira.log is:

2016-02-12 10:45:03,894 localhost-startStop-1 INFO      [c.a.jira.startup.LauncherContextListener] Memory Usage:

---------------------------------------------------------------------------------

Heap memory     :  Used:  281 MiB.  Committed:  510 MiB.  Max:  748 MiB

Non-heap memory :  Used:  174 MiB.  Committed:  189 MiB.  Max: 1264 MiB

---------------------------------------------------------------------------------

TOTAL           :  Used:  456 MiB.  Committed:  699 MiB.  Max: 2012 MiB

---------------------------------------------------------------------------------

2016-02-12 10:45:04,520 localhost-startStop-1 ERROR      [c.a.j.web.dispatcher.JiraWebworkActionDispatcher]

******************************************

JIRA startup failed, JIRA has been locked.

******************************************

2016-02-12 10:45:30,444 Modification Check:thread-1 INFO      [c.a.jira.startup.JiraStartupLogger]

___ Modifications ___________________________

Modified Files                                : jira-application.properties

Removed Files                                 : None

I hope any one can help me with my problem...

error.PNG

Bogdan Schreiber · Answer

I found my problem why the JIRA server doesnt start, I have implemented a wrong dependency in the pom.xml com.sun.jersey jersey-client 1.8 instead of this you have to use this one: com.atlassian.jira jira-rest-java-client 2.0.0-m2 provided all libraries of jersey are implemented in this dependency

Nic Brough -Adaptavist- · Answer

Something is stopping the system plugins from loading - sometimes this is resources on the server (you can increase the timeout, or give it more memory), but as you're writing an add-on, it suggests it's your add-on blocking the others.  Read further back up the log to find out what loading your add-on is doing.