Cannot shutdown JIRA due to NoClassDefFoundError org.apache.lucene.index.CompoundFileWriter

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

JIRA could not be shutdown despite running any of the stop-jira scripts. The following appears in the atlassian-jira.log:

013-12-12 20:09:34,695 Timer-2 INFO [jira.plugins.monitor.MonitorLauncher] Stopped JIRA monitoring
Dec 12, 2013 8:09:41 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-8080"]
Dec 12, 2013 8:09:41 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-8080"]
...
Exception in thread "QuartzScheduler_Worker-2" java.lang.NoClassDefFoundError: org/apache/lucene/index/CompoundFileWriter
at org.apache.lucene.index.DocumentsWriter.flush(DocumentsWriter.java:600)
at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:3543)
at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:3508)
at org.apache.lucene.index.IndexWriter.closeInternal(IndexWriter.java:1850)
at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1814)
at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1778)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.updateIndex(RevisionIndexer.java:303)
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)

Cause

The cause is currently unknown.

Resolution

  • Perform a reindex before shutting down JIRA.

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.