The Application Links health check has failed appears each time when you log in Jira DataCenter
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
When you log into Jira DataCenter, you might see the message, "The Application Links health check has failed in your system."
However, upon checking the Application Links section, you will find that it is indeed "CONNECTED," although there is a noticeable delay of over 30 seconds before this information appears.
Environment
Jira Data Center 9.12.x
Diagnosis
Set the logging level to DEBUG for the following packages using the Logging and Profiling page.
Choose the option to Configure logging level for another package. That will prompt you to specify the package and logging level.
1 2 3 4com.atlassian.plugins.navlink com.atlassian.applinks com.atlassian.oauth.consumer org.apache.httpThe following entries can be seen in the atlassian-jira logs.
1 2 3 4 5 6 7 8 9 10 112024-10-21 18:12:10,759+0200 http-nio-8080-exec-9 url: /rest/applinks/3.0/status/7bd07559-3cf3-3744-aff3-e97f083e9a35; user: aaaa DEBUG aaaa 1092x112641x2 oqkbaq 2002:705:705:a000::9,127.0.0.1 /rest/applinks/3.0/status/7bd07559-3cf3-3744-aff3-e97f083e9a35 [o.a.h.impl.conn.PoolingHttpClientConnectionManager] Connection leased: [id: 7376][route: {s}->https://confluence.atlassian.com:443][total available: 0; route allocated: 1 of 5; total allocated: 1 of 10] 2024-10-21 18:12:10,759+0200 http-nio-8080-exec-9 url: /rest/applinks/3.0/status/7bd07559-3cf3-3744-aff3-e97f083e9a35; user: aaaa DEBUG aaaa 1092x112641x2 oqkbaq 2002:705:705:a000::9,127.0.0.1 /rest/applinks/3.0/status/7bd07559-3cf3-3744-aff3-e97f083e9a35 [o.a.h.impl.execchain.MainClientExec] Opening connection {s}->https://confluence.atlassian.com:443 2024-10-21 18:12:10,759+0200 http-nio-8080-exec-9 url: /rest/applinks/3.0/status/7bd07559-3cf3-3744-aff3-e97f083e9a35; user: aaaa DEBUG aaaa 1092x112641x2 oqkbaq 2002:705:705:a000::9,127.0.0.1 /rest/applinks/3.0/status/7bd07559-3cf3-3744-aff3-e97f083e9a35 [o.a.h.impl.conn.DefaultHttpClientConnectionOperator] Connecting to confluence.atlassian.com/100.35.0.60:443 2024-10-21 18:12:10,759+0200 http-nio-8080-exec-9 url: /rest/applinks/3.0/status/7bd07559-3cf3-3744-aff3-e97f083e9a35; user: aaaa DEBUG aaaa 1092x112641x2 oqkbaq 2002:705:705:a000::9,127.0.0.1 /rest/applinks/3.0/status/7bd07559-3cf3-3744-aff3-e97f083e9a35 [o.a.h.conn.ssl.SSLConnectionSocketFactory] Connecting socket to confluence.atlassian.com/100.35.0.60:443 with timeout 10000 2024-10-21 18:12:20,784+0200 AppLinks ConcurrentExecutor:thread-15 DEBUG [o.a.h.impl.conn.DefaultHttpClientConnectionOperator] Connect to confluence.atlassian.com/100.35.0.60:443 timed out. Connection will be retried using another IP address 2024-10-21 18:12:20,784+0200 AppLinks ConcurrentExecutor:thread-15 DEBUG aaaa [o.a.h.conn.ssl.SSLConnectionSocketFactory] Connecting socket to confluence.atlassian.com/[2002:705:705:2000:0:0:0:78]:443 with timeout 10000 2024-10-21 18:12:20,785+0200 AppLinks ConcurrentExecutor:thread-15 DEBUG aaaa [o.a.h.conn.ssl.SSLConnectionSocketFactory] Enabled protocols: [TLSv1.3, TLSv1.2] 2024-10-21 18:12:20,785+0200 AppLinks ConcurrentExecutor:thread-15 DEBUG aaaa [o.a.h.conn.ssl.SSLConnectionSocketFactory] Enabled cipher suites:[TLS 2024-10-21 18:12:20,785+0200 AppLinks ConcurrentExecutor:thread-15 DEBUG aaaa [o.a.h.conn.ssl.SSLConnectionSocketFactory] Starting handshake
Cause
When Jira attempts to connect to a remote server, as shown in the above example with a Confluence server, it tries to reach http://confluence.atlassian.com/100.35.0.60:443. However, the connection timed out after 10 seconds. The subsequent log entry indicates an attempt to connect using the IPv6 address 2002:705:705:2000:0:0:0:78.
The Application Links health check pop-up message appears when the incoming application link is not reachable in a timely manner. As a result, the health check will fail.
Solution
There are two approches:
Ensure that IPv4 communication within the local network is configured correctly
Configure both applications (Jira and Confluence) to prioritize IPv6 communication. This is accomplished by adding the Java Virtual Machine (JVM) parameter below to the respective application configurations. Setting properties and options on startup
1"-Djava.net.preferIPv6Addresses=true"
Was this helpful?