com.atlassian.jira.exception.DataAccessException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • There is a spelling mistake of *esablish* which suppose to be *establish* in bq. Unable to esablish a connection with the database. Also, when we are at it, is it possible to further improve the error thrown to sent more clearer message? h4. Steps to reproduce: # Start JIRA that is connected to external database (eg. MySQL) # Go to Issue Navigator # Stop MySQL service # Click on one of the issue in the Issue Navigator h4. Error thrown: !esablish.PNG|thumbnail! {noformat} Cause: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.) Stack Trace: [hide] com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:94) at com.atlassian.jira.issue.managers.DefaultIssueManager.getIssue(DefaultIssueManager.java:114) at com.atlassian.jira.issue.managers.DefaultIssueManager.getIssueObject(DefaultIssueManager.java:306) at com.atlassian.jira.servlet.QuickLinkServlet.linkToIssue(QuickLinkServlet.java:139) at com.atlassian.jira.servlet.QuickLinkServlet.service(QuickLinkServlet.java:46) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243){noformat}
    via by Zulfadli Noor Sazali [Atlassian],
  • There is a spelling mistake of *esablish* which suppose to be *establish* in bq. Unable to esablish a connection with the database. Also, when we are at it, is it possible to further improve the error thrown to sent more clearer message? h4. Steps to reproduce: # Start JIRA that is connected to external database (eg. MySQL) # Go to Issue Navigator # Stop MySQL service # Click on one of the issue in the Issue Navigator h4. Error thrown: !esablish.PNG|thumbnail! {noformat} Cause: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.) Stack Trace: [hide] com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:94) at com.atlassian.jira.issue.managers.DefaultIssueManager.getIssue(DefaultIssueManager.java:114) at com.atlassian.jira.issue.managers.DefaultIssueManager.getIssueObject(DefaultIssueManager.java:306) at com.atlassian.jira.servlet.QuickLinkServlet.linkToIssue(QuickLinkServlet.java:139) at com.atlassian.jira.servlet.QuickLinkServlet.service(QuickLinkServlet.java:46) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243){noformat}
    via by Zulfadli Noor Sazali [Atlassian],
  • Upgrade from 3.4 fails with SQL Exception: 2006-03-10 16:07:00,040 ERROR [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: S QL Exception while executing the following:SELECT PE.PROPERTY_KEY, PE.ENTITY_NAME, PE.ID, PS.propertyvalue FROM propertyentry PE LEFT JOIN propertystring PS O N PE.ID = PS.ID WHERE PE.PROPERTY_KEY=? AND PE.ENTITY_NAME=? (ORA-00933: SQL command not properly ended ) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT PE.PROP ERTY_KEY, PE.ENTITY_NAME, PE.ID, PS.propertyvalue FROM propertyentry PE LEFT JOIN propertystring PS ON PE.ID = PS.ID WHERE PE.PROPERTY_KEY=? AND PE.ENTITY_NAM E=? (ORA-00933: SQL command not properly ended ) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:32) at com.atlassian.jira.user.util.UserUtilImpl.getUserLocalePreferenceEntries(UserUtilImpl.java:131) at com.atlassian.jira.user.util.UserUtilImpl.getUserLocalePreferenceCount(UserUtilImpl.java:122) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build125.doUpgrade(UpgradeTask_Build125.java:60) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:681) at com.atlassian.jira.upgrade.UpgradeManagerImpl.runUpgradeTasks(UpgradeManagerImpl.java:577) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgrade(UpgradeManagerImpl.java:403) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:351) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:311) at com.atlassian.jira.upgrade.UpgradeLauncher.contextInitialized(UpgradeLauncher.java:68) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3212) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3554) at org.apache.catalina.core.StandardHostDeployer.start(StandardHostDeployer.java:582) at org.apache.catalina.core.StandardHost.start(StandardHost.java:866) at org.apache.catalina.servlets.ManagerServlet.start(ManagerServlet.java:1056) at org.apache.catalina.servlets.HTMLManagerServlet.start(HTMLManagerServlet.java:506) at org.apache.catalina.servlets.HTMLManagerServlet.doGet(HTMLManagerServlet.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:696) at javax.servlet.http.HttpServlet.service(HttpServlet.java:809) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:200) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:146) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:209) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:144) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) :
    via by Eric Helfrich,
  • 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.
    via by Theo Tzidamis [Atlassian],
  • Upgrade from 3.4 fails with SQL Exception: 2006-03-10 16:07:00,040 ERROR [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: S QL Exception while executing the following:SELECT PE.PROPERTY_KEY, PE.ENTITY_NAME, PE.ID, PS.propertyvalue FROM propertyentry PE LEFT JOIN propertystring PS O N PE.ID = PS.ID WHERE PE.PROPERTY_KEY=? AND PE.ENTITY_NAME=? (ORA-00933: SQL command not properly ended ) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT PE.PROP ERTY_KEY, PE.ENTITY_NAME, PE.ID, PS.propertyvalue FROM propertyentry PE LEFT JOIN propertystring PS ON PE.ID = PS.ID WHERE PE.PROPERTY_KEY=? AND PE.ENTITY_NAM E=? (ORA-00933: SQL command not properly ended ) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:32) at com.atlassian.jira.user.util.UserUtilImpl.getUserLocalePreferenceEntries(UserUtilImpl.java:131) at com.atlassian.jira.user.util.UserUtilImpl.getUserLocalePreferenceCount(UserUtilImpl.java:122) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build125.doUpgrade(UpgradeTask_Build125.java:60) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:681) at com.atlassian.jira.upgrade.UpgradeManagerImpl.runUpgradeTasks(UpgradeManagerImpl.java:577) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgrade(UpgradeManagerImpl.java:403) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:351) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:311) at com.atlassian.jira.upgrade.UpgradeLauncher.contextInitialized(UpgradeLauncher.java:68) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3212) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3554) at org.apache.catalina.core.StandardHostDeployer.start(StandardHostDeployer.java:582) at org.apache.catalina.core.StandardHost.start(StandardHost.java:866) at org.apache.catalina.servlets.ManagerServlet.start(ManagerServlet.java:1056) at org.apache.catalina.servlets.HTMLManagerServlet.start(HTMLManagerServlet.java:506) at org.apache.catalina.servlets.HTMLManagerServlet.doGet(HTMLManagerServlet.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:696) at javax.servlet.http.HttpServlet.service(HttpServlet.java:809) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:200) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:146) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:209) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:144) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) :
    via by Eric Helfrich,
  • 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.
    via by Theo Tzidamis [Atlassian],
    • com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:94) at com.atlassian.jira.issue.managers.DefaultIssueManager.getIssue(DefaultIssueManager.java:114) at com.atlassian.jira.issue.managers.DefaultIssueManager.getIssueObject(DefaultIssueManager.java:306) at com.atlassian.jira.servlet.QuickLinkServlet.linkToIssue(QuickLinkServlet.java:139) at com.atlassian.jira.servlet.QuickLinkServlet.service(QuickLinkServlet.java:46) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:78)
    No Bugmate found.