The infra team have fixed the issue with Jira Linking.
(see below)
Ross
-------- Original Message --------
From: - Wed Sep 27 13:59:53 2006
X-Account-Key: account6
X-UIDL: 1159361765.28933.ns3.wkwyw.net,S=4500
X-Mozilla-Status: 0000
X-Mozilla-Status2: 00000000
Return-Path:
<[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 28930 invoked by uid 533); 27 Sep 2006 12:56:05 -0000
Received: from 209.237.227.194 by ns3.wkwyw.net (envelope-from
<[EMAIL PROTECTED]>, uid
92) with qmail-scanner-1.24-st-qms (spamassassin: 2.64. perlscan:
1.24-st-qms. Clear:RC:0(209.237.227.194):SA:0(?/?):. Processed in
3.075383 secs); 27 Sep 2006 12:56:05 -0000
X-Spam-Status: No, hits=? required=?
X-Antivirus-WKWYW.NET-Mail-From:
[EMAIL PROTECTED] via
ns3.wkwyw.net
X-Antivirus-WKWYW.NET: 1.24-st-qms
(Clear:RC:0(209.237.227.194):SA:0(?/?):. Processed in 3.075383 secs
Process 28917)
Received: from minotaur.apache.org (209.237.227.194) by ns3.wkwyw.net
with SMTP; 27 Sep 2006 12:56:01 -0000
Received: (qmail 38515 invoked by uid 1803); 27 Sep 2006 12:55:54 -0000
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 38408 invoked from network); 27 Sep 2006 12:55:52 -0000
Received: from hermes.apache.org (HELO mail.apache.org)
(209.237.227.199) by minotaur.apache.org with SMTP; 27 Sep 2006
12:55:52 -0000
Received: (qmail 10801 invoked by uid 500); 27 Sep 2006 12:55:50 -0000
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 10683 invoked by uid 500); 27 Sep 2006 12:55:50 -0000
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Post: <mailto:[EMAIL PROTECTED]>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Unsubscribe: <mailto:[EMAIL PROTECTED]>
List-Id: "Apache Infrastructure" <infrastructure.apache.org>
Delivered-To: mailing list [EMAIL PROTECTED]
Received: (qmail 10672 invoked by uid 99); 27 Sep 2006 12:55:50 -0000
Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org)
(140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Sep
2006 05:55:50 -0700
Authentication-Results: idunn.apache.osuosl.org
[EMAIL PROTECTED]; spf=permerror
X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=
Received-SPF: error (idunn.apache.osuosl.org: domain apache.org from
220.233.167.5 cause and error)
Received: from [220.233.167.5] ([220.233.167.5:25810]
helo=psyche.local) by idunn.apache.osuosl.org (ecelerity 2.1.1.8
r(12930)) with ESMTP id FD/D1-25968-CC47A154 for
<[EMAIL PROTECTED]>; Wed, 27 Sep 2006 05:55:42 -0700
Received: by psyche.local (Postfix, from userid 501) id 40695907743;
Wed, 27 Sep 2006 22:55:45 +1000 (EST)
Date: Wed, 27 Sep 2006 22:55:45 +1000
From: Jeff Turner <[EMAIL PROTECTED]>
To: Andrew McIntyre <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], David Blevins <[EMAIL PROTECTED]>
Subject: Re: Problem linking issues in JIRA?
Message-ID: <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Mail-Followup-To: Andrew McIntyre <[EMAIL PROTECTED]>,
[EMAIL PROTECTED], David Blevins <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.4.2.1i
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N
X-Antivirus: AVG for E-mail 7.1.407 [268.12.9/457]
On Tue, Sep 26, 2006 at 11:32:49PM -0700, Andrew McIntyre wrote:
Just now, I tried to link one JIRA issue to another (DERBY-1763 to
DERBY-883), and received this error:
An error occurred: com.atlassian.jira.exception.DataAccessException:
org.ofbiz.core.entity.GenericEntityException: while inserting:
[GenericEntity:IssueLink][destination,12348625][linktype,10030][source,12328186][sequence,null][id,12313548]
(SQL Exception while executing the following:INSERT INTO issuelink
(ID, LINKTYPE, SOURCE, DESTINATION, SEQUENCE) VALUES (?, ?, ?, ?, ?)
(Duplicate entry '12313548' for key 1))
Another Derby developer reported a similar issue earlier today. Any ideas?
Fixed, thanks.
David, something I completely forgot about..
There's a SEQUENCE_VALUE_ITEM table in JIRA that keeps track of the
maximum ID for all tables:
mysql> select * from SEQUENCE_VALUE_ITEM where SEQ_NAME='IssueLink';
+-----------+----------+
| SEQ_NAME | SEQ_ID |
+-----------+----------+
| IssueLink | 12313560 |
+-----------+----------+
1 row in set (0.00 sec)
So after all those issuelink inserts, the jelly script should run:
update SEQUENCE_VALUE_ITEM set SEQ_ID=${max} where SEQ_NAME='IssueLink';
Where ${max} is max(issuelink.ID)+1
--Jeff
thanks,
andrew
