com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, groupid, FIELDTYPE, FIELD, OLDVALUE, OLDSTRING, NEWVALUE, NEWSTRING FROM changeitem WHERE (groupid IN (?, ?, ?, ?, ?, ...) (ORA-01795: maximum number of expressions in a list is 1000)

Atlassian JIRA | Theo Tzidamis [Atlassian] | 5 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    h3. Symptoms JIRA will generate an error when trying to fetch a large number of change groups. This can happen when: # Fetching change history for a large number of issues. # Fetching change history for issues with a lot of change groups. The following can be found within the {{atlassian-jira.log}}: {noformat:title=SQL Server} com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, groupid, FIELDTYPE, FIELD, OLDVALUE, OLDSTRING, NEWVALUE, NEWSTRING FROM dbo.changeitem WHERE (groupid IN (?, ?, ?, ?, ?, ...) (Prepared or callable statement has more than 2000 parameter markers.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:120) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch.fetchAllChangeItems(ChangeHistoryBatch.java:160) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch.access$400(ChangeHistoryBatch.java:39) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch$BatchingChangeHistory.getChangeItems(ChangeHistoryBatch.java:272) {noformat} {noformat:title=Oracle} com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, groupid, FIELDTYPE, FIELD, OLDVALUE, OLDSTRING, NEWVALUE, NEWSTRING FROM changeitem WHERE (groupid IN (?, ?, ?, ?, ?, ...) (ORA-01795: maximum number of expressions in a list is 1000) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:120) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch.fetchAllChangeItems(ChangeHistoryBatch.java:160) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch.access$400(ChangeHistoryBatch.java:39) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch$BatchingChangeHistory.getChangeItems(ChangeHistoryBatch.java:272) {noformat} h3. Cause The {{ChangeHistoryBatch}} can build SELECT statements with excessively large IN clauses in JIRA 5.1, leading to errors in Activity Streams, GreenHopper, and other plugins that use the {{ChangeHistoryManager}}. h3. Workaround There is no current workaround at this stage.

    Atlassian JIRA | 5 years ago | Theo Tzidamis [Atlassian]
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, groupid, FIELDTYPE, FIELD, OLDVALUE, OLDSTRING, NEWVALUE, NEWSTRING FROM changeitem WHERE (groupid IN (?, ?, ?, ?, ?, ...) (ORA-01795: maximum number of expressions in a list is 1000)
  2. 0

    h3. Symptoms JIRA will generate an error when trying to fetch a large number of change groups. This can happen when: # Fetching change history for a large number of issues. # Fetching change history for issues with a lot of change groups. The following can be found within the {{atlassian-jira.log}}: {noformat:title=SQL Server} com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, groupid, FIELDTYPE, FIELD, OLDVALUE, OLDSTRING, NEWVALUE, NEWSTRING FROM dbo.changeitem WHERE (groupid IN (?, ?, ?, ?, ?, ...) (Prepared or callable statement has more than 2000 parameter markers.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:120) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch.fetchAllChangeItems(ChangeHistoryBatch.java:160) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch.access$400(ChangeHistoryBatch.java:39) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch$BatchingChangeHistory.getChangeItems(ChangeHistoryBatch.java:272) {noformat} {noformat:title=Oracle} com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, groupid, FIELDTYPE, FIELD, OLDVALUE, OLDSTRING, NEWVALUE, NEWSTRING FROM changeitem WHERE (groupid IN (?, ?, ?, ?, ?, ...) (ORA-01795: maximum number of expressions in a list is 1000) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:120) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch.fetchAllChangeItems(ChangeHistoryBatch.java:160) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch.access$400(ChangeHistoryBatch.java:39) at com.atlassian.jira.issue.changehistory.ChangeHistoryBatch$BatchingChangeHistory.getChangeItems(ChangeHistoryBatch.java:272) {noformat} h3. Cause The {{ChangeHistoryBatch}} can build SELECT statements with excessively large IN clauses in JIRA 5.1, leading to errors in Activity Streams, GreenHopper, and other plugins that use the {{ChangeHistoryManager}}. h3. Workaround There is no current workaround at this stage.

    Atlassian JIRA | 5 years ago | Theo Tzidamis [Atlassian]
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, groupid, FIELDTYPE, FIELD, OLDVALUE, OLDSTRING, NEWVALUE, NEWSTRING FROM changeitem WHERE (groupid IN (?, ?, ?, ?, ?, ...) (ORA-01795: maximum number of expressions in a list is 1000)

    Root Cause Analysis

    1. com.atlassian.jira.exception.DataAccessException

      org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, groupid, FIELDTYPE, FIELD, OLDVALUE, OLDSTRING, NEWVALUE, NEWSTRING FROM changeitem WHERE (groupid IN (?, ?, ?, ?, ?, ...) (ORA-01795: maximum number of expressions in a list is 1000)

      at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd()
    2. com.atlassian.jira
      ChangeHistoryBatch$BatchingChangeHistory.getChangeItems
      1. com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:120)
      2. com.atlassian.jira.issue.changehistory.ChangeHistoryBatch.fetchAllChangeItems(ChangeHistoryBatch.java:160)
      3. com.atlassian.jira.issue.changehistory.ChangeHistoryBatch.access$400(ChangeHistoryBatch.java:39)
      4. com.atlassian.jira.issue.changehistory.ChangeHistoryBatch$BatchingChangeHistory.getChangeItems(ChangeHistoryBatch.java:272)
      4 frames