Can't create Application Links
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
Summary
Problem
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:
1
2
3
4
5
6
7
ERROR [qtp1419166686-2777 ] com.atlassian.applinks.core.rest.ui.CreateApplicationLinkUIResource CreateApplicationLinkUIResource-tryToFetchManifest - ManifestNotFoundException thrown while retrieving manifest
com.atlassian.applinks.spi.manifest.ManifestNotFoundException: java.net.SocketTimeoutException: Read timed out
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1(AppLinksManifestDownloader.java:185)
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.access$000(AppLinksManifestDownloader.java:41)
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1$1.<init>(AppLinksManifestDownloader.java:83)
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:76)
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:73)Diagnosis
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.
1 2 3 4 5 6 7 8# 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 ^C --- <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 msMake sure your JIRA appllication is up and running. Make sure that the ports are on LISTEN.
1 2 3 4 5 6 7# 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:
1 2[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:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16[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:
1-Dhttp.proxyHost=proxy.mycompany.com -Dhttp.proxyPort=8080 -Dhttps.proxyHost=proxy.mycompany.com -Dhttps.proxyPort=8080
Cause
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.
Solution
Resolution
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
nonProxyHostsdirective for local connections so the proxy will be bypassed:1 2-Dhttp.nonProxyHosts="IP1|IP2|localhost|127.0.0.1" -Dhttps.nonProxyHosts="IP1|IP2|localhost|127.0.0.1"
Was this helpful?