Error during searcher initialization of the custom field
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
Summary
Symptoms
JIRA fails initialise custom field searcher, and the custom field itself, due to binary incompatibility with Jira platform. Since custom field initialization fails, it's not available in Jira.
The following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Caused by: java.lang.NoClassDefFoundError: org/apache/lucene/document/Fieldable
at com.tempoplugin.accounts.customfield.account.AccountCustomFieldSearcher.init(AccountCustomFieldSearcher.java:73) [?:?]
at com.tempoplugin.accounts.customfield.account.AccountCustomFieldSearcher.init(AccountCustomFieldSearcher.java:36) [?:?]
at com.atlassian.jira.issue.fields.ImmutableCustomField.loadCustomFieldSearcher(ImmutableCustomField.java:1784) [classes/:?]
at io.atlassian.fugue.Suppliers$MemoizingSupplier.get(Suppliers.java:175) [fugue-4.7.1.jar:?]
at com.atlassian.jira.issue.fields.ImmutableCustomField.getCustomFieldSearcher(ImmutableCustomField.java:1519) [classes/:?]
at com.atlassian.jira.issue.fields.ImmutableCustomField.createAssociatedSearchHandler(ImmutableCustomField.java:627) [classes/:?]
at com.atlassian.jira.issue.search.managers.DefaultSearchHandlerManager$SearchHandlerIndexer.indexSearchableField(DefaultSearchHandlerManager.java:478) [classes/:?]
at com.atlassian.jira.issue.search.managers.DefaultSearchHandlerManager$SearchHandlerIndexer.indexCustomField(DefaultSearchHandlerManager.java:461) [classes/:?]
at om.atlassian.jira.issue.search.managers.DefaultSearchHandlerManager.createHelper(DefaultSearchHandlerManager.java:278) [classes/:?]
at com.atlassian.jira.issue.search.managers.DefaultSearchHandlerManager.access$000(DefaultSearchHandlerManager.java:77) [classes/:?]
at com.atlassian.jira.issue.search.managers.DefaultSearchHandlerManager$1.get(DefaultSearchHandlerManager.java:102) [classes/:?]
at com.atlassian.jira.issue.search.managers.DefaultSearchHandlerManager$1.get(DefaultSearchHandlerManager.java:99) [classes/:?]
at com.atlassian.cache.memory.MemoryCacheManager$1$1.load(MemoryCacheManager.java:124) [atlassian-cache-memory-4.0.0-cdee60a.jar:?]
at com.atlassian.cache.memory.MemoryCacheManager$1$1.load(MemoryCacheManager.java:100) [atlassian-cache-memory-4.0.0-cdee60a.jar:?]
at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3528) [guava-26.0-jre.jar:?]
at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2277) [guava-26.0-jre.jar:?]
at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2154) [guava-26.0-jre.jar:?]
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2044) [guava-26.0-jre.jar:?]
... 389 moreDiagnosis
May have upgraded to Jira 8.0, but plugins are not upgraded yet (or not compatible).
Cause
Searcher initialization of the custom field fails due to binary incompatibility (NoClassDefFoundError) of plugin with Lucene API.
Solution
Workaround
Disable the plugin to avoid the error.
Resolution
Upgrade the plugin to version compatible with Jira you are using. If problem persist please contact Plugin Vendor.
Was this helpful?