Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-80139

Jira Issue Macro can fail to load in a clustered Confluence Data Center 7.13.10





      We've been able to reproduce the problem and can confirm it occurs when Confluence is cold started with 7.13.10 or with the upgrade JAR file for the Jira Issue Macro plugin.

      As a result of this, we've removed Confluence 7.13.10 from download, and have provided a workaround JAR file below in the Workaround section


      The Jira Issue Macro won't be displayed properly in a Confluence Data Center version 7.13.10


      Issue reproduced on Confluence Data Center version 7.13.10 (please note the issue has been seen on Clustered mode however in Standalone it is working fine)

      Steps to Reproduce

      • Create a new Confluence DC Clustered instance version 7.13.10
      • Connect to a Jira instance with Application Link
      • Attempt to display Jira Issues in Confluence using the Jira Issues Macro

      Expected Results

      The Jira Issues Macro should load fine

      Actual Results

      The Jira Issues Macros are failing

       We would also see the below stack trace appearing in the logs

      2022-10-13 16:40:46,009 ERROR [http-nio-21310-exec-5] [extra.jira.helper.JiraExceptionHelper] throwMacroExecutionException Macro execution exception: 
       -- url: /display/TEST/Test+Jira+Issues+Macro | page: 65609 | traceId: 369e4daf361f6002 | userName: admin | referer: confluenceBaseURL | action: viewpage
      com.atlassian.cache.CacheException: Problem retrieving a value from cache com.atlassian.confluence.extra.jira.services.DefaultAsyncJiraIssueBatchService
      Caused by: com.hazelcast.nio.serialization.HazelcastSerializationException: Failed to serialize 'com.atlassian.confluence.extra.jira.model.ClientId'
      Caused by: com.hazelcast.nio.serialization.HazelcastSerializationException: There is no suitable serializer for class com.atlassian.confluence.extra.jira.model.ClientId


      Due to the severity of this and a related issue, we've release a custom JAR file that includes a fix.

      To implement it, please

      1. Download the new file from https://packages.atlassian.com/maven-external/com/atlassian/confluence/plugins/confluence-jira-plugin/11.5.10/
        Please be careful when installing JAR files from the internet as they are executable code. In this case the JAR file is hosted on a known Atlassian domain, but we generally recommend against doing this
      2. In Confluence, click the Cog icon on the top right, and click Manage Apps
      3. On the Manage Apps page, click Upload App
      4. Select the downloaded JAR file, and click Upload
      5. Wait for the installation to complete
      6. Perform a rolling restart on the cluster (restarting one node, waiting for it to come back up, restarting the next node)
        This is required to fix an issue with a misconfigured cache

      Should you need to uninstall the app for any reason, please refer to Installing, Uninstalling, Upgrading and Downgrading Marketplace Apps on Confluence using REST API


      The issue was not present on Confluence DC 7.13.9


        Issue Links



              5337e069d1ab Pille Peri
              2e857505f334 Pascal Oberle
              13 Vote for this issue
              33 Start watching this issue