Builds tab in the Project Summary and inside issues doesn't load - Duplicate Key
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
The activity section inside issues (where the comments are displayed) is blank, and when trying to load the builds tab inside a project's summary page, JIRA throws:
The JIRA server was contacted but has returned an error response. We are unsure of the result of this operation
The following appears in the atlassian-jira.log when trying to update the Bamboo Configuration in the Application Link to Bamboo:
1
2
3
4
com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalArgumentException: duplicate key: EXAMPLE
at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
...
Diagnosis
Open the BambooConfiguration(Administration » Add-ons » Application Links » Bamboo Configuration), and verify if there are no duplicate keys in the Associated JIRA projects text box.
Cause
This problem happens due to the duplicate key. To avoid this problem from happening, we've raised BAMJ-109 - Avoid duplicate project key in Bamboo configuration page.
Solution
Resolution
To fix this problem, use the following SQL query to find the list of associations in the database:
1 2 3SELECT pe.id, pe.property_key, ps.propertyvalue FROM propertyentry pe JOIN propertystring ps ON pe.id = ps.id WHERE property_key LIKE '%jbam-associations';This will return something similar to:
1 2 3 4 5 6 7id | property_key | propertyvalue --------+-----------------------------------------------------------------------------+----------------- XXXXXX | applinks.application.236a00d0-b234-3b98-b769-3602565dafcb.jbam-associations | #java.util.List+ | | PROJA + | | PROJB + | | PROJC + | | PROJBAfter identifying it, update the
propertyvaluecolumn on thepropertystringtable using the ID returned so the duplicate key is removed.e.g.:
1 2 3 4UPDATE propertystring SET propertyvalue = '#java.util.List PROJA PROJB PROJC' WHERE id = XXXXXX;After applying this change, restart JIRA.
Was this helpful?