Builds tab in the Project Summary and inside issues doesn't load - Duplicate Key

Still need help?

The Atlassian Community is here for you.

Ask the community

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:

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 Bamboo Configuration (Administration » Add-ons » Application Links » Bamboo Configuration), and verify if there are no duplicate keys in the text box.

Cause

This problem happens due to the duplicate key. To avoid this problem from happening, we've raised BAMJ-109 - Getting issue details... STATUS .

Resolution

  1. To fix this problem, use the following SQL query to find the list of associations in the database:

    SELECT 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:

       id   |                                property_key                                 |  propertyvalue  
    --------+-----------------------------------------------------------------------------+-----------------
     XXXXXX | applinks.application.236a00d0-b234-3b98-b769-3602565dafcb.jbam-associations | #java.util.List+
            |                                                                             | PROJA          +
            |                                                                             | PROJB          +
            |                                                                             | PROJC          +
            |                                                                             | PROJB         
  2. After identifying it, update the propertyvalue column on the propertystring table using the ID returned so the duplicate key is removed.
    e.g.:

    UPDATE propertystring SET propertyvalue = '#java.util.List
    PROJA
    PROJB
    PROJC' WHERE id = XXXXXX;
  3. After applying this change, restart JIRA.
Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.