Indexing fails due to a modified jpm.xml file
Problem
JIRA Re-index does not complete and the following stack trace appears in the atlassian-jira.log
2015-07-07 18:31:14,193 IssueIndexer:thread-7 WARN admin 1111x234x1 3lsxrt 192.168.10.10 /secure/admin/IndexReIndex.jspa [atlassian.jira.index.AccumulatingResultBuilder] Name is null
java.lang.NullPointerException: Name is null
at java.lang.Enum.valueOf(Enum.java:236)
at com.atlassian.jira.index.DefaultIndexEngine$FlushPolicy.valueOf(DefaultIndexEngine.java:59)
at com.atlassian.jira.config.util.IndexWriterConfiguration$PropertiesAdaptor$1.getFlushPolicy(IndexWriterConfiguration.java:181)
at com.atlassian.jira.index.WriterWrapper.<init>(WriterWrapper.java:57)
at com.atlassian.jira.index.DefaultIndexEngine$DefaultWriterFactory.get(DefaultIndexEngine.java:322)
at com.atlassian.jira.index.DefaultIndexEngine$DefaultWriterFactory.get(DefaultIndexEngine.java:316)
at com.atlassian.jira.index.DefaultIndexEngine$WriterReference.doCreate(DefaultIndexEngine.java:299)
at com.atlassian.jira.index.DefaultIndexEngine$WriterReference.doCreate(DefaultIndexEngine.java:268)Cause
The jpm.xml file, which is placed at $JIRA_INSTALL/atlassian-jira/WEB-INF/classes folder, has been modified. This can be diagnosed upon checking the startup log entries on atlassian-jira.log or catalina.out.
___ Modifications ___________________________
Modified Files : log4j.properties, jira-application.properties,jpm.xmlResolution
Replace the modified jpm.xml with the original file corresponding to the JIRA version.
The original file can be found inside the JIRA .zip installer, available on the JIRA download page. If you are using an older version of JIRA, have a look at our Download Archives
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.