-
Bug
-
Resolution: Fixed
-
Low
-
7.6.2, 7.7.0, 7.12.3
-
7.06
-
7
-
Severity 3 - Minor
-
1
-
Summary
Issue is related to JRASERVER-62851. Currently, JIRA's default setting for jira.search.maxclauses is 65000. If JIRA has more than this amount in Unreleased Versions, boards will break with this error in the logs:
2018-02-06 11:48:37,512 http-nio-8080-exec-249 ERROR admin 708x7171733x2 m2if96 192.168.1.2,127.0.0.1 /rest/greenhopper/1.0/xboard/work/allData.json [c.a.g.service.issue.IssueDataServiceImpl] A the following query was too complex to generate a query from: {fixVersion in unreleasedVersions()}
com.atlassian.jira.issue.search.ClauseTooComplexSearchException: A the following query was too complex to generate a query from: {fixVersion in unreleasedVersions()}
at com.atlassian.jira.jql.query.DefaultLuceneQueryBuilder.createLuceneQuery(DefaultLuceneQueryBuilder.java:31)
at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.search(LuceneSearchProvider.java:203)
at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.search(LuceneSearchProvider.java:114)
at sun.reflect.GeneratedMethodAccessor1973.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26)
at com.sun.proxy.$Proxy184.search(Unknown Source)
... 2 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:136)
at com.sun.proxy.$Proxy184.search(Unknown Source)
at com.atlassian.greenhopper.service.issue.IssueDataServiceImpl.findImpl(IssueDataServiceImpl.java:166)
at com.atlassian.greenhopper.service.issue.IssueDataServiceImpl.findWithServiceOutcome(IssueDataServiceImpl.java:48)
at com.atlassian.greenhopper.web.rapid.work.WorkDataFactory.getWorkDataIssueCountAndLastUpdated(WorkDataFactory.java:213)
at com.atlassian.greenhopper.web.rapid.work.WorkDataFactory.getAllData(WorkDataFactory.java:120)
at com.atlassian.greenhopper.web.rapid.work.WorkResource$1.call(WorkResource.java:70)
at com.atlassian.greenhopper.web.rapid.work.WorkResource$1.call(WorkResource.java:59)
at com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:42)
at com.atlassian.greenhopper.web.AbstractResource.createResponse(AbstractResource.java:111)
at com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:91)
at com.atlassian.greenhopper.web.rapid.work.WorkResource.getPoolData(WorkResource.java:58)
... 2 filtered
Environment
JIRA 7.6.2, 7.7.0
Expected Results
JIRA open the board without any error.
Actual Results
JIRA throws Error readin issue data when user tries to access the board.
Workaround
See possible workarounds:
- Delete Kanban board sub-filter if you don't need versions
- If you need version, add specific project(s) related to JQL filter for the board into unreleasedVersions function
fixVersion in unreleasedVersions(ProjA, ProjB) OR fixVersion is EMPTY
- Release/archive versions until the system is under the 65000 limit
Not recommended. Increase the default limit of 65000, but it is not known how this will affect future performance of the system. This can be done by increasing the value for jira.search.maxclauses in jira-application.properties file located in following directory:
<JIRA-INSTALL-DIRECTORY><atlassian-jira>/WEB-INF/classes/
- It is not known how this will affect future performance of the system.
- is caused by
-
-
- Closed
-
-
JSEV-2580 Loading...
- is related to
-
-
- Closed
-
-
-
- Gathering Impact
-
- relates to
-
-
- Closed
-
-
-
- Closed
-