JIRA Startup Failed. JIRA has been locked

Victor G December 9, 2011

I was able to install JIRA and login initially. After login I received an error that the Gadgets Plugin was disabled. I went into the plugin section and enabled the plugin. I subsequently stopped the server and restarted. When restarting JIRA would not start with the following error.

JIRA Startup Failed

You cannot access JIRA at present. Look at the table below to identify the reasons

Description

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)

Embedded Gadgets Plugin (com.atlassian.gadgets.embedded)

Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard)

Atlassian JIRA - Plugins - Look And Feel Logo Upload Plugin (com.atlassian.jira.lookandfeel)

Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)

Gadget Spec Publisher Plugin (com.atlassian.gadgets.publisher)

Opensocial Plugin (com.atlassian.gadgets.opensocial)

9 answers

1 accepted

3 votes
Answer accepted
Victor G December 26, 2011

Turns out it was the antivirus that was running on the server. Once I shut if off, the plugins load fine.

Ramiro Pointis
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 2, 2012

So the antivirus was blocking the plugins and you can't turn it on when you use the Jira? What antivirus are you using? I have the same error and I'm using nod32.

1 vote
aschuma July 12, 2012

The following plugins are required by JIRA, but have not been started problem occurs in case JIRA is started with JDK 1.7.

****************
JIRA starting...
****************

2012-07-13 09:09:19,223 main INFO      [atlassian.jira.startup.JiraStartupLogger]

___ Environment _____________________________

     JIRA Build                                      : 4.4.4#664-r167664
     Build Date                                     : Sun Nov 27 00:00:00 MET 2011
     JIRA Installation Type                    : EAR/WAR
     Application Server                         : Apache Tomcat/6.0.35 - Servlet API 2.5
     Java Version                                  : 1.7.0_05 - Oracle Corporation <------------------------------

So make sure that 1.6 is used.

1 vote
grundic
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 9, 2011

Try this solution. I don't think, that problem in gadgets. Most likely, Jira was stopped incorrectly.

0 votes
KiranK July 14, 2014

Jira 6.2.7: setAssignee(user) not working. I applied in following way, Please suggest me.

Scenario:-

IssueManager issueManager = ComponentAccessor.getIssueManager();

CustomFieldManager customFieldManager = componentManager.getCustomFieldManager();

CustomField cf = customFieldManager.getCustomFieldObjectByName("Source User");

if (cf == null) {

log.error("No custom field found");

return;

}

User user = issue.getCustomFieldValue(cf);

if (user != null) {

User user2 = user.getDirectoryUser();

log.error("Setting assignee to: " + user2.getName());

log.error("Issue type : " + issue.getClass().getName());

MutableIssue mutableIssue = issueManager.getIssueObject(issue.id);

mutableIssue.setAssignee(user2);

mutableIssue.store();

}

0 votes
Gerry Tan July 14, 2014

Also check the stdout.log at jira_dir/logs. Another cause of this problem is the machine couldn't start the plugin until the timeout occur (often because machine is not powerful enough / ran out of cpu / ram). The plugin startup timeout can be adjusted by using java system property, see: https://confluence.atlassian.com/display/JIRAKB/JIRA+System+Plugin+Timeout+While+Waiting+for+Plugins+to+Enable

0 votes
Gerry Tan July 14, 2014

Had the same problem and as mentioned by others the cause was JAVA_HOME upgraded to jdk 7. Solution is to revert JIRA to use jdk 6. If installing jira as windows service:

  1. open admin-level command prompt to jira_directory\bin and run tomcat7w.exe //ES//jira_svc_name (the service name can be obtained from windows service properties)
  2. Go to Java tab, set Java Virtual Machine to jira_directory\jre\bin\server\jvm.dll
  3. Restart jira service
0 votes
MB
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 7, 2013

I also had this same issue. Reverting JDK to 1.6 solved it. Thanks a lot.

0 votes
Ricardo Batista February 4, 2012

What if the problem continues? Windows 7 (atlassian-jira-4.4.4).

File: catalina.2012-02-04

4/Fev/2012 21:58:29 org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.1.20.
4/Fev/2012 21:58:29 org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
4/Fev/2012 21:58:29 org.apache.catalina.startup.SetAllPropertiesRule begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'minSpareThreads' to '25' did not find a matching property.
4/Fev/2012 21:58:29 org.apache.catalina.startup.SetAllPropertiesRule begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'maxSpareThreads' to '75' did not find a matching property.
4/Fev/2012 21:58:33 org.apache.coyote.http11.Http11AprProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
4/Fev/2012 21:58:33 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 8696 ms
4/Fev/2012 21:58:34 org.apache.catalina.realm.JAASRealm setContainer
INFO: Set JAAS app name Catalina
4/Fev/2012 21:58:34 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
4/Fev/2012 21:58:34 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
4/Fev/2012 22:07:10 org.apache.coyote.http11.Http11AprProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
4/Fev/2012 22:07:14 org.apache.catalina.startup.Catalina start
INFO: Server startup in 519005 ms

File: access_log

127.0.0.1 1327x1x1 - [04/Feb/2012:22:07:57 +0000] "GET / HTTP/1.1" 302 - 42308 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1328x2x1 - [04/Feb/2012:22:08:21 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 12402 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1328x3x1 - [04/Feb/2012:22:08:22 +0000] "GET /favicon.ico HTTP/1.1" 302 - 0 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1328x4x1 - [04/Feb/2012:22:08:22 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 18 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1331x5x1 - [04/Feb/2012:22:11:23 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 80 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1335x6x1 - [04/Feb/2012:22:15:17 +0000] "GET / HTTP/1.1" 302 - 0 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1335x7x1 - [04/Feb/2012:22:15:17 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 0 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1335x8x1 - [04/Feb/2012:22:15:17 +0000] "GET /favicon.ico HTTP/1.1" 302 - 0 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1335x9x1 - [04/Feb/2012:22:15:17 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 0 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1341x10x1 - [04/Feb/2012:22:21:05 +0000] "GET / HTTP/1.1" 302 - 10 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"
127.0.0.1 1341x11x1 - [04/Feb/2012:22:21:06 +0000] "GET /JiraLockedError HTTP/1.1" 200 3833 20 "-" "Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0" "-"

0 votes
grundic
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 9, 2011

Okay, the problem could be in plugin - just now rolled such situation. Jira was complaining about unsatisfied dependency for injecting class. Try to search for some kind of exception during Jira start up.

Hope it helps..

Suggest an answer

Log in or Sign up to answer