Slow response in JIRA due to failed Fisheye connection
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
JIRA's responsiveness is slow. Particular actions noted to be affected are:
Transitioning issues through workflow steps
Viewing issues
The following appears in the atlassian-jira.log:
1
2
3
2013-04-25 09:33:39,614 localhost-startStop-1 WARN [jirafisheyeplugin.domain.fisheye.FishEyeManagerImpl] Error retrieving repositories for 'http://fisheye:8060/'
java.io.IOException: Error in remote call to 'FishEye / Crucible' (http://fisheye:8060) [AbstractRestCommand{path='api/rest/repositories', params={}, methodType=POST}] : Connection refused: connect
at com.atlassian.jirafisheyeplugin.rest.FishEyeRestApiManagerImpl.callFisheye(FishEyeRestApiManagerImpl.java:196)
OR
1
2
3
2013-04-29 16:39:17,660 main WARN [jirafisheyeplugin.domain.fisheye.FishEyeManagerImpl] Error encountered resolving Crucible projects for 'http://fisheye:8060/'
java.io.IOException: Error in remote call to 'FishEye / Crucible' (http://fisheye:8060) [AbstractRestCommand{path='rest-service/projects-v1', params={excludeAllowedReviewers=true}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)
at com.atlassian.jirafisheyeplugin.rest.FishEyeRestApiManagerImpl.callFisheye(FishEyeRestApiManagerImpl.java:194)Cause
The connection from JIRA to Fisheye is broken, which is causing a slower response in JIRA at every time there is an attempted call made to the Fisheye server.
Workaround/Resolution
As a temporary fix; disable the Fisheye Application Link, by going to JIRA's Administration > Application Links page and click the Disable link for the applicable application. A more long term solution is required to prevent future slow downs due to failed connections between JIRA and Fisheye.
Was this helpful?