JIRA applications Subversion plugin is not updating commits due to "SimpleFSLock lock obtain timeout IOException" on index directory
Symptoms
Commits are no longer updating on issues in my JIRA applications.
The following appears in the atlassian-jira.log:
2014-05-06 13:28:31,062 QuartzScheduler_Worker-1 WARN ServiceRunner com.atlassian.jira.plugin.ext.subversion.revisions.scheduling.UpdateIndexMonitorImpl:job [ext.subversion.revisions.RevisionIndexer] Unable to index repository 'XXXXXX'
java.io.IOException: Problem with path <JIRA-HOME>/caches/indexes/plugins/atlassian-subversion-revisions: Lock obtain timed out: SimpleFSLock@<JIRA-HOME>/caches/indexes/plugins/atlassian-subversion-revisions/write.lock
at com.atlassian.jira.plugin.ext.subversion.revisions.DefaultLuceneIndexAccessor.getIndexWriter(DefaultLuceneIndexAccessor.java:48)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.updateIndex(RevisionIndexer.java:266)
at com.atlassian.jira.plugin.ext.subversion.revisions.scheduling.UpdateIndexTask.execute(UpdateIndexTask.java:34)
at com.atlassian.sal.jira.scheduling.JiraPluginSchedulerService.run(JiraPluginSchedulerService.java:94)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@<JIRA-HOME>/caches/indexes/plugins/atlassian-subversion-revisions/write.lock
at org.apache.lucene.store.Lock.obtain(Lock.java:84)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1115)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:932)
at com.atlassian.jira.plugin.ext.subversion.revisions.DefaultLuceneIndexAccessor.getIndexWriter(DefaultLuceneIndexAccessor.java:41)
... 7 moreCause
JIRA applications are unable to obtain a lock on the Subversion plugin so is not able to update commits in the index. It possible that users may encounter the below bugs:
- Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Resolution
- Verify that only one Subversion Service exists in the JIRA application, as detailed in Services. If there is more than one, delete all of them except for one.
- Ensure that the user running JIRA has write access to the JIRA-HOME directory, and all subdirectories and files contained within.
- Stop your JIRA application.
- Delete the
<JIRA-HOME>/caches/indexes/plugins/atlassian-subversion-revisionsdirectory. - Start your JIRA application. Upon startup, provided the service is installed, an index of the JIRA applications Subversion repositories will commence.
- Check the permission of the same directory
<JIRA-HOME>/caches/indexes/plugins/atlassian-subversion-revisionsafter it is recreated, whether it allow user that is running JIRA to read and write the files.
Last modified on Nov 9, 2016
Powered by Confluence and Scroll Viewport.