Request url '{bamboo url}' isn't in the same origin as the rpc url '{bamboo url:port}'

[Zhiming Zhang]

Jira complained that application link failure after we moved our Bamboo server to 8085 port (still on the same server) today. We put the port after the application url and it showed connected then. 

However, I noticed some of issues showing: 

JIRA is having difficulty contacting {Bamboo server}. If this condition persists, please contact your JIRA administrators.

I looked at log and found the following error: 

/rest/dev-status/1.0/issue/summary [plugin.devstatus.provider.DefaultCoordinator] {Bamboo server} (java.lang.IllegalArgumentException: Request url 'http://{Bamboo server url}/rest/remote-link-aggregation/latest/aggregation?globalId={issue key}&globalId={issue key}' isn't in the same origin as the rpc url 'http://{Bamboo server url}:8085')

It seems Jira is still trying to retrieve build information from old URL. 

Please help, thanks.

[Andy Heinzer · Accepted solution]

What versions of Jira and Bamboo are you using? 

I suspect it might just be that some other process in Jira might still be using a cached value for the previous URL.  If that was the case, then you should be able to restart the Jira application in order to fix this.  Doing this will clear the existing caches that exist for the application.

If a restart of the Jira application does not resolve this problem then it might be worth more closely exploring the specific versions you are using.  I was able to find that some older versions of Jira could produce this error in a bug.  Please see https://jira.atlassian.com/browse/JRASERVER-37781 for details.  However that bug was fixed in the 6.3.3 version, so that version or newer versions should already contain this fix.

[Zhiming Zhang]

Thanks for the reply, Andrew. It turned out that it was caching. So restart resolved the issue. 

[Gaurav Agrawal]

@Andy Heinzer How to clear cache for Jira Cloud? I face same issue with Jira Cloud to Bitbucket App links.

[Andy Heinzer]

Jira Cloud is a stateless application.  As such, it does not have a start/restart aspect that Jira Server has.  There is also no means for a site-admin to clear such a cache either. 

If you encounter this problem specifically on a Jira Cloud site, then I would recommend creating a support case if you have support (free plan sites do not have the ability to do this per our support offerings). 

If you also happen to be using a free plan for Jira Cloud, please let me know some more details about this, such as your site URL, and the date/time in which you saw this particular error.  Perhaps I can investigate this further.

[Gaurav Agrawal]

Hello Andy, Thanks for the reply. Please check https://getsupport.atlassian.com/servicedesk/customer/portal/48/PCS-52496