com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Resolution][id,10100][sequence,7][description,][name,Trying to put the resolution name to be longer than 60 characters and see if that will throw an error or something] (SQL Exception while executing the following:INSERT INTO resolution (ID, SEQUENCE, pname, DESCRIPTION, ICONURL) VALUES (?, ?, ?, ?, ?) (Data truncation: Data too long for column 'pname' at row 1))

Atlassian JIRA | Zulfadli Noor Sazali [Atlassian] | 3 years ago
  1. 0

    The following are thrown in the {{atlassian-jira.log}} {noformat}com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Resolution][id,10100][sequence,7][description,][name,Trying to put the resolution name to be longer than 60 characters and see if that will throw an error or something] (SQL Exception while executing the following:INSERT INTO resolution (ID, SEQUENCE, pname, DESCRIPTION, ICONURL) VALUES (?, ?, ?, ?, ?) (Data truncation: Data too long for column 'pname' at row 1)) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:393) at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.createValue(WrappingOfBizDelegator.java:206){noformat} Basically the {{pname}} column for {{resolution}} table has a limit of 60 characters, which can easily be updated in the database to have it more than 60 characters. Instead of showing the following image/page !error.png! It would be nicer to have a warning saying something like the following {quote}The 'resolution' name is too long. Please enter a shorter name.{quote}

    Atlassian JIRA | 3 years ago | Zulfadli Noor Sazali [Atlassian]
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Resolution][id,10100][sequence,7][description,][name,Trying to put the resolution name to be longer than 60 characters and see if that will throw an error or something] (SQL Exception while executing the following:INSERT INTO resolution (ID, SEQUENCE, pname, DESCRIPTION, ICONURL) VALUES (?, ?, ?, ?, ?) (Data truncation: Data too long for column 'pname' at row 1))
  2. 0

    The following are thrown in the {{atlassian-jira.log}} {noformat}com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Resolution][id,10100][sequence,7][description,][name,Trying to put the resolution name to be longer than 60 characters and see if that will throw an error or something] (SQL Exception while executing the following:INSERT INTO resolution (ID, SEQUENCE, pname, DESCRIPTION, ICONURL) VALUES (?, ?, ?, ?, ?) (Data truncation: Data too long for column 'pname' at row 1)) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:393) at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.createValue(WrappingOfBizDelegator.java:206){noformat} Basically the {{pname}} column for {{resolution}} table has a limit of 60 characters, which can easily be updated in the database to have it more than 60 characters. Instead of showing the following image/page !error.png! It would be nicer to have a warning saying something like the following {quote}The 'resolution' name is too long. Please enter a shorter name.{quote}

    Atlassian JIRA | 3 years ago | Zulfadli Noor Sazali [Atlassian]
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Resolution][id,10100][sequence,7][description,][name,Trying to put the resolution name to be longer than 60 characters and see if that will throw an error or something] (SQL Exception while executing the following:INSERT INTO resolution (ID, SEQUENCE, pname, DESCRIPTION, ICONURL) VALUES (?, ?, ?, ?, ?) (Data truncation: Data too long for column 'pname' at row 1))
  3. 0

    h3. Steps to reproduce # Start with JIRA < 6.2-OD-3/icebat-85.0. # Create a custom issue status, which is created with an ID of 10000. # Upgrade to JIRA 6.2-OD-3/icebat-85.0. # Try to create another issue status, and you'll receive a stack trace: {code} com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Status][id,10000][sequence,12][description,null][name,A New Status][statuscategory,1][iconurl,/images/icons/statuses/generic.png] (SQL Exception while executing the following:INSERT INTO public.issuestatus (ID, SEQUENCE, pname, DESCRIPTION, ICONURL, STATUSCATEGORY) VALUES (?, ?, ?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_issuestatus")) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:395) at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.createValue(WrappingOfBizDelegator.java:219) at com.atlassian.jira.config.AbstractIssueConstantsManager.createConstant(AbstractIssueConstantsManager.java:38) at com.atlassian.jira.config.DefaultStatusManager.createStatus(DefaultStatusManager.java:73) at com.atlassian.jira.bc.config.DefaultStatusService.createStatus(DefaultStatusService.java:75) at com.atlassian.jira.web.action.admin.statuses.ViewStatuses.addConstant(ViewStatuses.java:196) at com.atlassian.jira.web.action.admin.constants.AbstractViewConstants.doAddConstant(AbstractViewConstants.java:42) at com.atlassian.jira.web.action.admin.statuses.ViewStatuses.doAddStatus(ViewStatuses.java:134) 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 webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) [...] {code} Try to create it a second time and it'll work fine, as the new status is then created with an ID of 10001. The more custom issue statuses already exist in an instance, the more times you have to click Add in order to get past the latest ID. h3. Workaround If on OnDemand contact support, support will: # Shutdown JIRA # Backup the database # Identify the current maximum value of the issuestatus id {noformat} select id::integer from issuestatus order by id desc limit 1; {noformat} # Update the sequence_value_item table to define the Status sequence ID as 1 higher than the value identified in the previous step {noformat} update sequence_value_item set seq_id = <value from above + 1> where seq_name = 'Status'; {noformat} # Start JIRA back up.

    Atlassian JIRA | 3 years ago | Nick Mason [Atlassian]
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Status][id,10000][sequence,12][description,null][name,A New Status][statuscategory,1][iconurl,/images/icons/statuses/generic.png] (SQL Exception while executing the following:INSERT INTO public.issuestatus (ID, SEQUENCE, pname, DESCRIPTION, ICONURL, STATUSCATEGORY) VALUES (?, ?, ?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_issuestatus"))
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    h3. Steps to reproduce # Start with JIRA < 6.2-OD-3/icebat-85.0. # Create a custom issue status, which is created with an ID of 10000. # Upgrade to JIRA 6.2-OD-3/icebat-85.0. # Try to create another issue status, and you'll receive a stack trace: {code} com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Status][id,10000][sequence,12][description,null][name,A New Status][statuscategory,1][iconurl,/images/icons/statuses/generic.png] (SQL Exception while executing the following:INSERT INTO public.issuestatus (ID, SEQUENCE, pname, DESCRIPTION, ICONURL, STATUSCATEGORY) VALUES (?, ?, ?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_issuestatus")) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:395) at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.createValue(WrappingOfBizDelegator.java:219) at com.atlassian.jira.config.AbstractIssueConstantsManager.createConstant(AbstractIssueConstantsManager.java:38) at com.atlassian.jira.config.DefaultStatusManager.createStatus(DefaultStatusManager.java:73) at com.atlassian.jira.bc.config.DefaultStatusService.createStatus(DefaultStatusService.java:75) at com.atlassian.jira.web.action.admin.statuses.ViewStatuses.addConstant(ViewStatuses.java:196) at com.atlassian.jira.web.action.admin.constants.AbstractViewConstants.doAddConstant(AbstractViewConstants.java:42) at com.atlassian.jira.web.action.admin.statuses.ViewStatuses.doAddStatus(ViewStatuses.java:134) 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 webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) [...] {code} Try to create it a second time and it'll work fine, as the new status is then created with an ID of 10001. The more custom issue statuses already exist in an instance, the more times you have to click Add in order to get past the latest ID. h3. Workaround If on OnDemand contact support, support will: # Shutdown JIRA # Backup the database # Identify the current maximum value of the issuestatus id {noformat} select id::integer from issuestatus order by id desc limit 1; {noformat} # Update the sequence_value_item table to define the Status sequence ID as 1 higher than the value identified in the previous step {noformat} update sequence_value_item set seq_id = <value from above + 1> where seq_name = 'Status'; {noformat} # Start JIRA back up.

    Atlassian JIRA | 3 years ago | Nick Mason
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Status][id,10000][sequence,12][description,null][name,A New Status][statuscategory,1][iconurl,/images/icons/statuses/generic.png] (SQL Exception while executing the following:INSERT INTO public.issuestatus (ID, SEQUENCE, pname, DESCRIPTION, ICONURL, STATUSCATEGORY) VALUES (?, ?, ?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_issuestatus"))
  6. 0

    h3. Steps to reproduce # Start with JIRA < 6.2-OD-3/icebat-85.0. # Create a custom issue status, which is created with an ID of 10000. # Upgrade to JIRA 6.2-OD-3/icebat-85.0. # Try to create another issue status, and you'll receive a stack trace: {code} com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Status][id,10000][sequence,12][description,null][name,A New Status][statuscategory,1][iconurl,/images/icons/statuses/generic.png] (SQL Exception while executing the following:INSERT INTO public.issuestatus (ID, SEQUENCE, pname, DESCRIPTION, ICONURL, STATUSCATEGORY) VALUES (?, ?, ?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_issuestatus")) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:395) at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.createValue(WrappingOfBizDelegator.java:219) at com.atlassian.jira.config.AbstractIssueConstantsManager.createConstant(AbstractIssueConstantsManager.java:38) at com.atlassian.jira.config.DefaultStatusManager.createStatus(DefaultStatusManager.java:73) at com.atlassian.jira.bc.config.DefaultStatusService.createStatus(DefaultStatusService.java:75) at com.atlassian.jira.web.action.admin.statuses.ViewStatuses.addConstant(ViewStatuses.java:196) at com.atlassian.jira.web.action.admin.constants.AbstractViewConstants.doAddConstant(AbstractViewConstants.java:42) at com.atlassian.jira.web.action.admin.statuses.ViewStatuses.doAddStatus(ViewStatuses.java:134) 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 webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) [...] {code} Try to create it a second time and it'll work fine, as the new status is then created with an ID of 10001. The more custom issue statuses already exist in an instance, the more times you have to click Add in order to get past the latest ID. h3. Workaround If on OnDemand contact support, support will: # Shutdown JIRA # Backup the database # Identify the current maximum value of the issuestatus id {noformat} select id::integer from issuestatus order by id desc limit 1; {noformat} # Update the sequence_value_item table to define the Status sequence ID as 1 higher than the value identified in the previous step {noformat} update sequence_value_item set seq_id = <value from above + 1> where seq_name = 'Status'; {noformat} # Start JIRA back up.

    Atlassian JIRA | 3 years ago | Ben Sewell
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Status][id,10000][sequence,12][description,null][name,A New Status][statuscategory,1][iconurl,/images/icons/statuses/generic.png] (SQL Exception while executing the following:INSERT INTO public.issuestatus (ID, SEQUENCE, pname, DESCRIPTION, ICONURL, STATUSCATEGORY) VALUES (?, ?, ?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_issuestatus"))

    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

      org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Resolution][id,10100][sequence,7][description,][name,Trying to put the resolution name to be longer than 60 characters and see if that will throw an error or something] (SQL Exception while executing the following:INSERT INTO resolution (ID, SEQUENCE, pname, DESCRIPTION, ICONURL) VALUES (?, ?, ?, ?, ?) (Data truncation: Data too long for column 'pname' at row 1))

      at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue()
    2. com.atlassian.jira
      DefaultOfBizDelegator.createValue
      1. com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:393)
      1 frame