Upgrading JIRA subversion plugin fails due to subversion indexes
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Upon upgrading the JIRA Subversion plugin, the Subversion Commits tab does not populate with commits
The following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
2012-08-28 07:51:54,292 QuartzWorker-0 ERROR ServiceRunner Subversion Revision Indexing Service [ext.subversion.revisions.RevisionIndexService] Error indexing changes: com.atlassian.jira.issue.index.IndexException: Problem with path jira-home\caches\indexes\plugins\atlassian-subversion-revisions: no segments* file found in org.apache.lucene.store.MMapDirectory@\jira-home\caches\indexes\plugins\atlassian-subversion-revisions lockFactory=org.apache.lucene.store.SimpleFSLockFactory@62ff5057: files: []
com.atlassian.jira.issue.index.IndexException: Problem with path \jira-home\caches\indexes\plugins\atlassian-subversion-revisions: no segments* file found in org.apache.lucene.store.MMapDirectory@C:\J\caches\indexes\plugins\atlassian-subversion-revisions lockFactory=org.apache.lucene.store.SimpleFSLockFactory@62ff5057: files: []
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.updateLastRevisionIndexed(RevisionIndexer.java:391)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.updateIndex(RevisionIndexer.java:258)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService.run(RevisionIndexService.java:32)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: org.apache.lucene.index.IndexNotFoundException: no segments* file found in org.apache.lucene.store.MMapDirectory@jira-home\caches\indexes\plugins\atlassian-subversion-revisions lockFactory=org.apache.lucene.store.SimpleFSLockFactory@62ff5057: files: []
at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:711)
at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:75)
at org.apache.lucene.index.IndexReader.open(IndexReader.java:428)
at org.apache.lucene.index.IndexReader.open(IndexReader.java:274)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.updateLastRevisionIndexed(RevisionIndexer.java:386)Cause
The subversion indexes need to be rebuilt upon upgrading the plugin.
Resolution
Shutdown JIRA
Remove the
atlassian-subversion-revisionsdirectory fromjira-home\caches\indexes\pluginsMake sure to delete the actual atlassian-subversion-revisions directory and not just its content
Check that the JIRA user has write access to the JIRA home directory
Start JIRA
Reindex your JIRA just to confirm whether the indexes has been properly rebuilt.
Was this helpful?