Details
-
Bug
-
Resolution: Fixed
-
Low
-
8.0.3, 7.13.12, 8.5.3, 8.7.1
-
7.13
-
3
-
Severity 2 - Major
-
2
-
Description
Issue Summary
Searching for issues in a project/projects which are associated with more than 2100 custom field local config schemas can cause 500 HTTP error.
Steps to Reproduce
- Set up Jira with MS SQL database,
- Create more than 2100 configuration schemes for custom fields which are assigned to project
- Search for the issues in those projects
Expected Results
There are no SQLServerException and users can search for the issue.
Actual Results
The below exception is thrown in the atlassian-jira.log file:
14:30:17,954 http-nio2-8080-exec-74 url:/issues/ url:/secure/IssueNavAction!default.jspa username:XXXXXX ERROR XXXXXX 870x4121352x3 XXXXXX localhost /issues/ Servlet.service() for servlet [action] threw exceptioncom.microsoft.sqlserver.jdbc.SQLServerException: The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258) at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1535) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:467) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:409) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7151) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2478) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:219) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:199) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:331) at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:83) at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:83) at com.querydsl.sql.AbstractSQLQuery.fetch(AbstractSQLQuery.java:446) at com.atlassian.jira.issue.search.searchers.renderer.IssueTypeSearchRenderer.selectOptions(IssueTypeSearchRenderer.java:281) at com.atlassian.jira.issue.search.searchers.renderer.IssueTypeSearchRenderer.lambda$getVisibleIssueTypeIdsWithCssInfo$3(IssueTypeSearchRenderer.java:207) at com.atlassian.jira.issue.search.searchers.renderer.IssueTypeSearchRenderer.lambda$null$4(IssueTypeSearchRenderer.java:222)
Workaround
Reduce the number of local custom field configuration schema