Setting up Application Link results in ServerID already being used
Problem
Trying to set up an Application Link with an Atlassian application results in:
The ServerID reported is already being used for an Application Link. This may be because you have multiple applications with the same ServerID.
Diagnosis
This error may occur when trying to migrate any Atlassian application server or setting up a development environment with existing data. The stack trace may look like the following:
java.lang.IllegalArgumentException: Application with server ID 30a2a7ec-3233-30e9-87a2-edf1dfc0c4e4 is already configured
at com.atlassian.applinks.core.DefaultApplicationLinkService.addApplicationLink(DefaultApplicationLinkService.java:272)Cause
Application Links uses the Server ID as a unique identifier.
Workaround
Manually change the Server ID by following:
- Change the server ID for an instance of Jira server for JIRA
- Changing Server ID for Bitbucket Server Cloned Instances for Bitbucket Server
How to change the server ID of Confluence for Confluence
Resolution
Atlassian's development team is aware of this issue and is looking into it, see here: Unable to locate Jira server for this macro. It may be due to Application Link configuration.
The final resolution will be to upgrade to the fixed version (once it is released).
Last modified on Aug 19, 2020
Powered by Confluence and Scroll Viewport.