Details
-
Bug
-
Resolution: Fixed
-
Medium
-
4.0 - Beta 1
-
standalone
-
4
-
Description
After an unclean shutdown of jira the .jira-home.loc stays in place for ever and prevents jira from working.
It would be nicer if jira could detect if the lock file is held by an active instance.
Attachments
Issue Links
- is duplicated by
-
JRASERVER-19659 It seems that JIRA does not always remove the jira-home lock file when the WAR edition is stopped/restarted.
- Closed
-
JRASERVER-20311 .jira-home.lock not removed when restarting Windows in a virtualised environment
- Closed
-
JRASERVER-23762 Jira does not release home directory lock if DB connection refused on startup
- Closed
-
JRASERVER-17848 JIRA lockfile left after unclean shutdowns, prevents startup
- Closed
- is related to
-
JRASERVER-17600 Jira keeps locked due to .jira-home.lock is not removed if jira is stoped by closing startup.bat window
- Closed
-
JRASERVER-20311 .jira-home.lock not removed when restarting Windows in a virtualised environment
- Closed
-
JRASERVER-19799 Stand-alone JIRA shut down script does not wait until JIRA and container exit before continuing increases odds of unclean shut down
- Closed
- relates to
-
JRASERVER-23762 Jira does not release home directory lock if DB connection refused on startup
- Closed