Cannot change ComponentManager status from NOT_STARTED to PLUGINSYSTEM_STARTED

Ricardo Almeida June 5, 2017

Since we've upgraded our server from Win 2012R2 to Win 2016 every time the server is restarted, JIRA Server presents the message "Cannot change ComponentManager status from NOT_STARTED to PLUGINSYSTEM_STARTED". I have to restart the Jira Service to keep it working again.

I had already changed the Startup Type from "Automatic" to "Automatic (delayed start)", no changes on this strange behaviour.

Is anybody else facing the same issue? Any hints?

1 answer

0 votes
Ricardo Almeida June 5, 2017

Inspecting the logfile, we've found this message:

JIRA-Bootstrap ERROR      [c.a.jira.startup.ComponentContainerLauncher] A fatal error occurred during initialisation. JIRA has been locked.
com.atlassian.plugin.osgi.container.OsgiContainerException: Unable to clean the cache directory: C:\Program Files\Atlassian\Application Data\JIRA\plugins\.osgi-plugins\felix

The strange thing is that a restart on service succeeds, without cnahging any security permissions on this folder.

 

Suggest an answer

Log in or Sign up to answer