We are making enhancements to an existing JIRA application. As part of the enhancements, we are adding a new field to an issue type. For all the existing issues of this issue type, we set the default value through SQL by inserting value in JIRA database table directly. We shutdown JIRA before executing the SQL and once SQL is executed we bring the JIRA server up and do reindex.
But when we access the JIRA system we get one time error depending on what action we do.
2015-04-23 00:21:52,490 http-bio-8080-exec-23 ERROR dravimat 21x8526x1 1mgn5q7 10.200.80.10,10.200.80.25 /secure/QuickCreateIssue.jspa [onresolve.jira.groovy.GroovyRunner] The script failed : javax.script.ScriptException: javax.script.ScriptException: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:IssueLink][id,30078][source,32811][sequence,0][linktype,10003][destination,32808] (SQL Exception while executing the following:INSERT INTO issuelink (ID, LINKTYPE, SOURCE, DESTINATION, SEQUENCE) VALUES (?, ?, ?, ?, ?) (ORA-00001: unique constraint (ETO_JIRA.PK_ISSUELINK) violated
But once this error (any one) occurs, after that the error won't come again. The system works fine.
How to avoid the error happening first time? How it is automatically getting cleared from next time?
Looking at the table being affected, it seems like its something related with Issue Links. Can you check if you link one issue to another if the same error occurs in your logs?
Also, that behaviour seems like the one described here: https://confluence.atlassian.com/display/JIRAKB/Duplicated+Entry+-+Unique+Constraint+Violated
Maybe the queries there help you to identify the root problem?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG