Can't create Application Links

Still need help?

The Atlassian Community is here for you.

Ask the community

Trying to establish an application link between Fisheye/Crucible and JIRA (or another Atlassian product) fails.

The following appears in the atlassian-fisheye-YYYY-MM-DD.log and it means that Fisheye/Crucible can't reach the other application due to a network issue or the other application's unavailability:

ERROR [qtp1419166686-2777 ] CreateApplicationLinkUIResource-tryToFetchManifest - ManifestNotFoundException thrown while retrieving manifest
com.atlassian.applinks.spi.manifest.ManifestNotFoundException: Read timed out
	at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1(
	at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.access$000(
	at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1$1.<init>(
	at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(
	at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(

Try running connectivity tests and check for proxy configurations on your Fisheye/Crucible or JIRA (or the other Atlassian product) instances. Make sure all the tests below pass and you can identify additional configuration:

  • Make sure you can ping each other's IP address. 

    # ping <JIRA_IP_ADDRESS>
    PING <JIRA_IP_ADDRESS> (<JIRA_IP_ADDRESS>) 56(84) bytes of data.
    64 bytes from <JIRA_IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.026 ms
    64 bytes from <JIRA_IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.024 ms
    --- <JIRA_IP_ADDRESS> ping statistics ---
    2 packets transmitted, 2 received, 0% packet loss, time 1696ms
    rtt min/avg/max/mdev = 0.024/0.025/0.026/0.001 ms
  • Make sure your JIRA appllication is up and running. Make sure that the ports are on LISTEN. 

    # Check if JIRA is listening on its standard port
    # netstat -an |grep 8443
    tcp        0      0 :::8443                     :::*                        LISTEN
    # Check if FishEye/Crucible is listening on its standard port
    # netstat -an |grep 8060
    tcp        0      0 :::8060                     :::*                        LISTEN
  • Check that there are no rules in the Iptables (or Windows firewall) in which JIRA or Fisheye/Crucible is running: 

    [root@wsc-voo-151 ~]# service iptables status
    iptables: Firewall is not running.
  • Make sure you're able to telnet JIRA's IP:PORT from Fisheye/Crucible and vice-versa. The outputs below show successful connections: 

    [root@wsc-voo-151 ~]# telnet localhost 8443
    Trying ::1...
    Connected to localhost.
    Escape character is '^]'.
    telnet> quit
    Connection closed.
    [root@wsc-voo-151 ~]# telnet localhost 7990
    Trying ::1...
    Connected to localhost.
    Escape character is '^]'.
    telnet> quit
    Connection closed.
  • Verify if you have configured an Outound proxy for your system. Check your Fisheye/Crucible environment variable FISHEYE_OPTS for configurations similar to the one below: -Dhttp.proxyPort=8080 -Dhttps.proxyPort=8080
  • JIRA is not up and running. Make sure to get JIRA up and running.
  • The port number in use by the JIRA (or any other Atlassian application) is either blocked by an Iptables rule or Firewall or proxy or it could be disabled by the Operating System.
  • An Outbound proxy could be causing the AppLinks to fail.
  • Get the network or server administrator to unblock the port.
  • If you need Outbound proxy, for some reason, and you're trying to establish a direct connection between Fisheye/Crucible and JIRA, make sure you include nonProxyHosts directive for local connections so the proxy will be bypassed:


Last modified on Jul 31, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.