Fisheye delay / Exceptions & cluttered logs


We are experiencing two issues with our Jira installation. At first catalina.out seems to be cluttered with the following warning:

  • 012-11-16 11:15:10,438 http-8443-81 WARN "jira-username" 675x315927x1 k5x383 "ip" /browse/OEP [atlassian.applinks.core.DefaultApplicationLinkService] Couldn't load type salesforce for application link with id 9ad95ed3-d1f8-3bf2-98c4-ad88fb83aef9. Type is not installed?

It seems like an issue with the connector for Saleforce.

The second issue is that any time a user attempts to view a ticket and open the source tab the following Exception is thrown and a delay occurs before the commit information is properly shown:

  • 012-11-16 11:21:25,243 http-8443-81 ERROR "jira-username" 681x319658x1 dnyfyj "ip" /rest/tabs/1.0/com.atlassian.jirafisheyeplugin:fisheye-issuepanel/OEP-11244 [web.issuetabpanel.fisheye.FishEyeIssueTabPanel] Problem retrieving Crucible projects Error in remote call to 'FishEye 0 ("http://fisheye:port)' ("http://fisheye:port") [AbstractRestCommand{path='rest-service/projects-v1', params={excludeAllowedReviewers=true}, methodType=GET}] : Received status code 404 (Not Found)

Again this looks like an issue with the fisheye plugin.

Any ideas?

P.S We are using fisheye-plugin v.3.4.12 and Jira v.4.4.3

1 answer

0 votes


The first error seems to be related to JIRA x Salesforce Plugin. According to the plugin page, only versions 4.1.4-37167 and 4.1.5-38113 of this plugin are compatible with JIRA 4.4.3. Could you please check if you're using one of these versions?

If you are not, please make sure to use one of these versions.

If you are, please note that this is a 3rd-party plugin, supported by Go2Group, so any problems related to this plugin must be discussed with them.

As for the second error, the plugin version 3.4.12 is compatible with JIRA 4.4.3. Could you please let me know if your FishEye/Crucible instance version is between 2.4.1 and 2.9.2? These are the versions compatible with version 3.4.12 of the plugin.

The error message is saying that JIRA could not find the FisHEye instance. Could you please check:

  • If FishEye is up and running?
  • If you're using the correct authentication method? Please note that it depends on the number of users in each of the instances.
  • If you indeed need to use Trusted Applications, check if you've configured the JIRA FishEye Plugin according to this page (IP Patterns and URL Patterns)

If the problem persists, please open a support ticket.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,506 views 15 20
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you