Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-16296

Large number of request type causes, SQL exception error parameter limit "The server supports a maximum of 2100 parameters"

XMLWordPrintable

      Issue Summary

      With large number of request type in JSM, transition of issues would lead to an exception "The server supports a maximum of 2100 parameters". The UI would have this error “org.ofbiz.core.entity.GenericTransactionException: Commit failed, rollback previously requested by nested transaction.”

      The same behaviour is impacting the SLA view with exception as well at the end point "/browse/XXXXXX-1234567, /secure/ProjectIssueNavigatorAction!issueViewWithSidebar"

      Steps to Reproduce

      1. Setup JSM with customer portal.
      2. Add over 2200 Request Type.
      3. Try to transition a issue from the project with these large number of Request Type

      Expected Results

      The transition should work fine.

      Actual Results

      The below exception is thrown in the atlassian-jira.log file:

      /secure/AjaxIssueAction.jspa [c.a.s.internal.util.SafeRunner] 
      Unable to run event handler onIssueChangedEvent: IssueChangedEventImpl{
          changeItems=[
              com.atlassian.jira.issue.history.ChangeItemBean@3d5db8e7[
                  fieldType=custom,
                  field=Start Date,
                  from=<null>,
                  fromString=<null>,
                  to=2025-06-18,
                  toString=18/Jun/25,
                  created=2025-06-18 06:48:06.28
              ],
              com.atlassian.jira.issue.history.ChangeItemBean@10f73b66[
                  fieldType=jira,
                  field=status,
                  from=1,
                  fromString=Backlog,
                  to=3,
                  toString=Work in Progress,
                  created=2025-06-18 06:48:06.28
              ]
          ],
          author=Optional[kguthri(kguthri)],
          comment=Optional.empty,
          issue=GTPISNSDDI-31169,
          eventTime=Wed Jun 18 06:48:06 PDT 2025,
          sendMail=true,
          spanningOperation=null
      }com.atlassian.cache.CacheException: com.querydsl.core.QueryException: 
      Caught SQLServerException for select "AO_54307E_VIEWPORTFORM"."CALL_TO_ACTION", ... 
      // SQL Query details truncated for brevity    
          at com.atlassian.cache.ehcache.DelegatingCache.get(DelegatingCache.java:133)
          at com.atlassian.servicedesk.internal.feature.customer.request.requesttype.RequestTypeInternalManagerImpl.loadValidRequestTypes(RequestTypeInternalManagerImpl.java:395)
          at com.atlassian.servicedesk.internal.feature.customer.request.requesttype.RequestTypeInternalServiceImpl.loadValidRequestTypes(RequestTypeInternalServiceImpl.java:342)
          ...
          (additional stack trace lines)
          ...Caused by: com.querydsl.core.QueryException: 
      Caught SQLServerException for select "AO_54307E_VIEWPORTFORM"."CALL_TO_ACTION", ...
      // SQL Query details truncated for brevity    at com.querydsl.sql.DefaultSQLExceptionTranslator.translate(DefaultSQLExceptionTranslator.java:50)
          at com.querydsl.sql.Configuration.translate(Configuration.java:459)
          at com.querydsl.sql.AbstractSQLQuery.fetch(AbstractSQLQuery.java:502)
          ...
          (additional stack trace lines)
          ...Caused by: com.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:265)
          at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1676)
          at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:615)
          ...
          (additional stack trace lines)
          ... 
       /browse/XXXXXX-1234567, /secure/ProjectIssueNavigatorAction!issueViewWithSidebar.jspa; user: vn549vn ERROR vn549vn 332x10923966x6 txh7rz 10.72.186.181 /browse/ETOOLS-121954 [c.a.j.web.component.ModuleWebComponentImpl] An exception occured while rendering the web panel: com.atlassian.servicedesk.frontend-webpack-plugin:sla-web-panel (null)
      com.atlassian.cache.CacheException: com.querydsl.core.QueryException: Caught SQLServerException for select "AO_54307E_VIEWPORTFORM"."CALL_TO_ACTION", "AO_54307E_VIEWPORTFORM"."DESCRIPTION", "AO_54307E_VIEWPORTFORM"."FORM_ORDER", "AO_54307E_VIEWPORTFORM"."ICON", "AO_54307E_VIEWPORTFORM"."ICON_ID", "AO_54307E_VIEWPORTFORM"."ID", "AO_54307E_VIEWPORTFORM"."INTRO", "AO_54307E_VIEWPORTFORM"."ISSUE_TYPE_ID", "AO_54307E_VIEWPORTFORM"."KEY", "AO_54307E_VIEWPORTFORM"."NAME", "AO_54307E_VIEWPORTFORM"."VIEWPORT_ID" from "dbo"."AO_54307E_VIEWPORTFORM" "AO_54307E_VIEWPORTFORM" inner join "dbo"."AO_54307E_VIEWPORT" "AO_54307E_VIEWPORT" on "AO_54307E_VIEWPORTFORM"."VIEWPORT_ID" = "AO_54307E_VIEWPORT"."ID" where ("AO_54307E_VIEWPORTFORM"."VIEWPORT_ID" in (?,...TRUNCATED...?)) and ("AO_54307E_VIEWPORTFORM"."ISSUE_TYPE_ID" in (select cast("issuetype"."ID" as bigint) from "dbo"."issuetype" "issuetype")) order by "AO_54307E_VIEWPORT"."NAME" asc, "AO_54307E_VIEWPORTFORM"."FORM_ORDER" asc
      	at com.atlassian.cache.ehcache.DelegatingCache.get(DelegatingCache.java:133) 

       

      Workaround

      Required, if there is no workaround please state:
      Currently there is no known workaround for this behavior. A workaround will be added here when available

              bornatowski Bartosz Ornatowski
              dsidhpura@atlassian.com Deepak Sidhpura
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: