com.atlassian.jira.exception.DataAccessException: Error occurred while storing issue.

Atlassian JIRA | Bogdan Dziedzic [Atlassian] | 8 years ago
  1. 0

    In a situation where JIRA fails to create a new issue from an email processed by the mail handler, the issue ID is not reused. So for e.g. if your currently available issue ID is TST-10 and JIRA for whatever reason fails to process an email that should use this issue ID, JIRA will try to assign to the next new issue issue ID TST-11. The issue ID TST-10 is lost and not reused by the system, which in a busy JIRA installation can generate a thousand issue ID gap . On the top of missing issues ID, the following error in the log file helps to identify this issue. BTW. This error can be addressed by configuring the system with consistent character encoding (JVM, JDBC and DB). {noformat} Caused by: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Issue][summary,Zoom: Text][status,1][votes,0][assignee,admin][security,null][type,1][timespent,null][id,21769][reporter,test][project,10022][environment,null][created,2008-06-03 14:49:36.912][updated,2008-06-03 14:49:36.912][priority,3][description,Zoom: Text: sr02 ? sr03 ? sr04 ? sr05 ? sr06 ? sr07 ? sr08 ? sr09 ? sr10 ? sr11 test test test ][workflowId,21889][timeestimate,null][duedate,null][timeoriginalestimate,null][key,TEST-11512] (SQL Exception while executing the following:INSERT INTO public.jiraissue (ID, pkey, PROJECT, REPORTER, ASSIGNEE, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, VOTES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (ERROR: character 0xc297 of encoding "UTF8" has no equivalent in "WIN1252")) at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:123) at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:88) at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:63) at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:480) at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:460) at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:77) at com.atlassian.core.ofbiz.util.EntityUtils.createValue(EntityUtils.java:61) at com.atlassian.jira.issue.IssueImpl.store(IssueImpl.java:927) ... 20 more 2008-06-03 14:49:36,943 JiraQuartzScheduler_Worker-0 ERROR [service.util.handler.CreateIssueHandler] Could not create issue! com.atlassian.jira.exception.DataAccessException: Error occurred while storing issue. at com.atlassian.jira.issue.IssueImpl.store(IssueImpl.java:944) at com.atlassian.jira.workflow.function.issue.IssueCreateFunction.execute(IssueCreateFunction.java:72) at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:869) at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1265) at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:618) {noformat}

    Atlassian JIRA | 8 years ago | Bogdan Dziedzic [Atlassian]
    com.atlassian.jira.exception.DataAccessException: Error occurred while storing issue.
  2. 0

    In a situation where JIRA fails to create a new issue from an email processed by the mail handler, the issue ID is not reused. So for e.g. if your currently available issue ID is TST-10 and JIRA for whatever reason fails to process an email that should use this issue ID, JIRA will try to assign to the next new issue issue ID TST-11. The issue ID TST-10 is lost and not reused by the system, which in a busy JIRA installation can generate a thousand issue ID gap . On the top of missing issues ID, the following error in the log file helps to identify this issue. BTW. This error can be addressed by configuring the system with consistent character encoding (JVM, JDBC and DB). {noformat} Caused by: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Issue][summary,Zoom: Text][status,1][votes,0][assignee,admin][security,null][type,1][timespent,null][id,21769][reporter,test][project,10022][environment,null][created,2008-06-03 14:49:36.912][updated,2008-06-03 14:49:36.912][priority,3][description,Zoom: Text: sr02 ? sr03 ? sr04 ? sr05 ? sr06 ? sr07 ? sr08 ? sr09 ? sr10 ? sr11 test test test ][workflowId,21889][timeestimate,null][duedate,null][timeoriginalestimate,null][key,TEST-11512] (SQL Exception while executing the following:INSERT INTO public.jiraissue (ID, pkey, PROJECT, REPORTER, ASSIGNEE, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, VOTES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (ERROR: character 0xc297 of encoding "UTF8" has no equivalent in "WIN1252")) at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:123) at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:88) at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:63) at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:480) at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:460) at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:77) at com.atlassian.core.ofbiz.util.EntityUtils.createValue(EntityUtils.java:61) at com.atlassian.jira.issue.IssueImpl.store(IssueImpl.java:927) ... 20 more 2008-06-03 14:49:36,943 JiraQuartzScheduler_Worker-0 ERROR [service.util.handler.CreateIssueHandler] Could not create issue! com.atlassian.jira.exception.DataAccessException: Error occurred while storing issue. at com.atlassian.jira.issue.IssueImpl.store(IssueImpl.java:944) at com.atlassian.jira.workflow.function.issue.IssueCreateFunction.execute(IssueCreateFunction.java:72) at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:869) at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1265) at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:618) {noformat}

    Atlassian JIRA | 8 years ago | Bogdan Dziedzic [Atlassian]
    com.atlassian.jira.exception.DataAccessException: Error occurred while storing issue.
  3. 0

    Hi Bob, We are using atlassian-cli-3.9.0 and JIRA version 5.4.12. We are using following command to delete some projects: jira --action deleteProject --project "prokjectKey" The above command is working fine for most of the projects but in some cases this fails to delete projects. We have experienced following error in JIRA log: ------------------- 2016-05-08 10:54:44,476 http-bio-8080-exec-118 ERROR anonymous 638x278692x1 - 172.18.16.166,172.18.13.241,172.18.14.165 /rpc/soap/jirasoapservice-v2 [atlassian.jira.project.DefaultProjectManager] Exception removing issues com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Generic Entity Exception occurred in deleteByAnd (SQL Exception while executing the following:DELETE FROM moved_issue_key WHERE ISSUE_ID=? (Deadlock found when trying to get lock; try restarting transaction)) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.removeByAnd(DefaultOfBizDelegator.java:311) ---------------------- On command line interface we are getting below error message: --------------------- Remote error: ; nested exception is: java.net.SocketException: Connection reset Sun May 8 10:43:36 GMT 2016 Could not deleted Project with key: AU --------------------- Once we checked the database, then we found that some of the projects are not deleted but some of them were deleted in spite of these errors. So my question is that can you please confirm that whether these deleted projects are deleted successfully along with their related data or only partial data were removed of deleted projects as during deletion we were getting above error. Can you please suggest any solution in order to prevent these errors, as we have so many projects (about 1600) to delete. Thanks, Reetesh

    JIRA | 7 months ago | Reetesh Kumar
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Generic Entity Exception occurred in deleteByAnd (SQL Exception while executing the following:DELETE FROM moved_issue_key WHERE ISSUE_ID=? (Deadlock found when trying to get lock; try restarting transaction))
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Version name: "this is not a version" Stack trace: 2011-11-07 16:52:30,110 http-8080-13 INFO admin 1012x1084x2 1mhke8u 172.20.9.85 /rest/greenhopper/1.0/release [greenhopper.service.version.ReleaseServiceImpl] creating versions in projects: [Project: ARA, Project: BULK, Project: XSS] 2011-11-07 16:52:30,126 http-8080-13 ERROR admin 1012x1084x2 1mhke8u 172.20.9.85 /rest/greenhopper/1.0/release [greenhopper.service.version.ReleaseServiceImpl] org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Version][id,10040][project,10031 ][description,URGHH][sequence,6][name,this is not a version][releasedate,2011-11-07 00:00:00.0] (SQL Exception while executing the following:INSERT INTO public.projectversion (ID, PROJECT, vname, DESCRIPTION, SEQUENCE, RELEASED, ARCHIVED, URL, RELEASEDATE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_projectversion")) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Version][id,10040][project,10031][description,URGHH][sequence,6][name,this is not a version][releasedate,2011-11-07 00:00:00.0] (SQL Exception while executing the following:INSERT INTO public.projectversion (ID, PROJECT, vname, DESCRIPTION, SEQUENCE, RELEASED, ARCHIVED, URL, RELEASEDATE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_projectversion")) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:365) at com.atlassian.jira.project.version.OfBizVersionStore.createVersion(OfBizVersionStore.java:35) at com.atlassian.jira.project.version.CachingVersionStore.createVersion(CachingVersionStore.java:79) at com.atlassian.jira.project.version.DefaultVersionManager.createVersion(DefaultVersionManager.java:118) at com.atlassian.jira.bc.project.version.DefaultVersionService.createVersion(DefaultVersionService.java:528) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$AbstractMultiTenantAwareInvocationHandler.invokeInternal(MultiTenantComponentFactoryImpl.java:181) at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$MultiTenantAwareInvocationHandler.invoke(MultiTenantComponentFactoryImpl.java:211) at $Proxy185.createVersion(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129) at $Proxy185.createVersion(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154) at $Proxy185.createVersion(Unknown Source) at com.atlassian.greenhopper.service.version.VersionServiceImpl.createVersions(VersionServiceImpl.java:79)

    Atlassian JIRA | 5 years ago | Kara Hatherly
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Version][id,10040][project,10031][description,URGHH][sequence,6][name,this is not a version][releasedate,2011-11-07 00:00:00.0] (SQL Exception while executing the following:INSERT INTO public.projectversion (ID, PROJECT, vname, DESCRIPTION, SEQUENCE, RELEASED, ARCHIVED, URL, RELEASEDATE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_projectversion"))

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.atlassian.jira.exception.DataAccessException

      Error occurred while storing issue.

      at com.atlassian.jira.issue.IssueImpl.store()
    2. com.atlassian.jira
      IssueCreateFunction.execute
      1. com.atlassian.jira.issue.IssueImpl.store(IssueImpl.java:944)
      2. com.atlassian.jira.workflow.function.issue.IssueCreateFunction.execute(IssueCreateFunction.java:72)
      2 frames
    3. com.opensymphony.workflow
      AbstractWorkflow.initialize
      1. com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:869)
      2. com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1265)
      3. com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:618)
      3 frames