Details
-
Bug
-
Resolution: Answered
-
Medium
-
None
-
3.11
-
3.11
-
3
-
Description
If the index directory doesn't exist when you start JIRA, everything appears normal until the point you search for issues. Then JIRA blows up with a very unfriendly stacktrace:
Cause: org.apache.jasper.JasperException: java.io.FileNotFoundException: no segments* file found in org.apache.lucene.store.FSDirectory@/home/jturner/tmpjira/cleandb/ent/3.11/index/issues: files: Stack Trace: [hide] org.apache.jasper.JasperException: java.io.FileNotFoundException: no segments* file found in org.apache.lucene.store.FSDirectory@/home/jturner/tmpjira/cleandb/ent/3.11/index/issues: files: at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:512) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:395) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) ....
I think we need to detect that indexing is disabled and print a nice message, pointing people to the Indexing admin page where they can reenable it.