Error "This application has the same ID" in create application link jira & confluence

[Hamid Gholami]

Dear Sir/Madam,

We are trying to connect JIRA 7.9.2 to Confluence 5.8.8.

At the first try for connecting the instances, they get connected successfully, but after deleting the existing link we could not connect JIRA to Confluence anymore, and the following error message appeared:

This application has the same ID as myself. Can't create link to myself.

This issue happened for our Crucible instance as well.

Regards,

Hamid 

[Danyal Iqbal]

Are they running on the same server? try to configure the link while logged in locally.

See https://confluence.atlassian.com/kb/setting-up-application-link-results-in-serverid-already-being-used-284368474.html for further analysis.

Check out https://ecosystem.atlassian.net/browse/APL-629 and please upgrade your servers. 7.9 and 5.8 are still supported but still buggier than the latest release :)

[Danyal Iqbal]

If you want to get your hands dirty , you can try the resolutions proposed here- changing server id:

https://confluence.atlassian.com/jirakb/changing-server-id-for-test-installations-285839562.html

[Hamid Gholami]

Thanks

They are not on the same server.

What do you mean by log in locally? we tested it with internal user log in, but the issue remained the same.

[Hamid Gholami]

According to your advice we changed server ID but this problem still persists.

[Hamid Gholami]

Dear,

May we have an update regarding this matter ?!?

best regards,

HAMID

[Danyal Iqbal]

Hi hamid,

Are you using a Load balancer/reverse proxy in front of these servers? Do you have apache/http-server in front of your applications? How are they configured? Are the application residing in their own context?

Please double check if the serverID was actually updated?(restart the application and have a look in the db).

If the serverID was indeed changed and you are still recieving the same error message, this is an infrastructure misconfiguration issue... your server.xml/virtual host config files might be misconfigured. You can post  your server.xml here and I can review it quickly, but I would definitely suggest opening a support request with atlassian. The support team should be able to help you out. (analyse the logs, and the config files.)