Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-65610

Application link health check fails with spurious network error

XMLWordPrintable

      Atlassian Update – 11-22-2018

      This bug is related to the Atlassian Troubleshooting and Support Tools plugin, and it is currently being tracked in the Ecosystem request ATST-923. Please direct any feedback related to this bug to that request.

      Best regards,
      René Chiquete - Atlassian Support.

      Summary

      Health Check is returning an error when connecting JIRA 7.4.0 to Confluence 5.9.5 although the application link is working according to the 2 following points:

      • in JIRA Admin > Applications > Application Links, the status of the Application Link is "Connected"
      • when trying to link a Confluence page to a JIRA issue from the Link dialog, the Confluence page is properly connected

      Steps to Reproduce

      1. Install JIRA 7.4.0
      2. Install Confluence 5.9.5
      3. Create an Application link to Confluence from the JIRA UI
      4. Go to JIRA Admin > System > Support Tools
      5. Click on "Services" to expand it
      6. Click on "Application Links" to expand it

      Expected Results

      The result should be "Your application links are all working properly", as it's the case when linking JIRA to Confluence 6.3.1.

      Actual Results

      The result says "One of your application links is reporting "Network error".", although the application link is working and it is possible to link Confluence pages to JIRA issues:

      Also, when navigating to any other JIRA page, a pop-up shows at the top-right corner with a similar error:

      Lastly, we can see the following warning in the JIRA logs:

      2017-07-13 12:25:16,020 HealthCheck:thread-6 WARN      [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link 'df6813a6-ecd0-3c00-8c59-1673445a2fc4'

      NOTE

      It should be clearer which AppLinks versions are compatible with each other:

      • JIRA 7.4.0 is using AppLinks 5.3.2 while Confluence 5.9.5 is using AppLinks 5.0.4, and in the Application links version matrix documentation, it is not clear whether 5.3.2 is supposed to be compatible with 5.0.4.

      If there is any incompatibility issue, it should be clearly specified in this documentation.

      Workaround

      It's reported that upgrading Confluence to the latest version may help, but this is not guaranteed as there's also a report that JIRA 7.4.4 shows the same warning connecting to Confluence 6.3.4.

       If there's no actual applinks problem, the warning may just be ignored or dismissed.

        1. LinkWithinIssueToConfluence5.9.5.png
          LinkWithinIssueToConfluence5.9.5.png
          177 kB
        2. JIRA_ApplicationLinkToConfluence5.9.5.png
          JIRA_ApplicationLinkToConfluence5.9.5.png
          147 kB
        3. HealthCheckPopUp_Confluence5.9.5.png
          HealthCheckPopUp_Confluence5.9.5.png
          240 kB
        4. HealthCheck_Confluence6.3.1.png
          HealthCheck_Confluence6.3.1.png
          268 kB
        5. HealthCheck_Confluence5.9.5.png
          HealthCheck_Confluence5.9.5.png
          266 kB
        6. 1.JPG
          1.JPG
          30 kB

            [JRASERVER-65610] Application link health check fails with spurious network error

            Jamie Simon added a comment -

            Same issue affecting my company. Jira Service Desk 7.11.2.

            Jamie Simon added a comment - Same issue affecting my company. Jira Service Desk 7.11.2.

            Dov Frankel added a comment -

            I'm not able to vote or comment on ATST-923. Looks like it's read-only to the public.

            Dov Frankel added a comment - I'm not able to vote or comment on ATST-923. Looks like it's read-only to the public.

            Rebecca C added a comment -

            I can't seem to vote for this issue or the associated ATST issue but this is affecting my team.

            Rebecca C added a comment - I can't seem to vote for this issue or the associated ATST issue but this is affecting my team.

            Rene C. [Atlassian Support] added a comment -

            Hello swh.tpe.ms! This bug ticket is currently closed as it belongs to the Atlassian Troubleshooting and Support Tools plugin, and it is currently being tracked under https://ecosystem.atlassian.net/browse/ATST-923. I suggest directing any feedback related to this bug to that request.

            Best regards,
            René Chiquete - Atlassian Support.

            Rene C. [Atlassian Support] added a comment - Hello swh.tpe.ms ! This bug ticket is currently closed as it belongs to the Atlassian Troubleshooting and Support Tools plugin, and it is currently being tracked under https://ecosystem.atlassian.net/browse/ATST-923 . I suggest directing any feedback related to this bug to that request. Best regards, René Chiquete - Atlassian Support.

            TPE added a comment - - edited

            Using Jira 7.12.1 with application links to Confluence 6.3.1, Bitbucket 5.10.1 and Fisheye 4.6.0 we are getting the same warnings.
            In a AO_..._HEALTH_CHECK_STATUS table we can see that the error logged is "One of your application links is reporting "Network error."

            TPE added a comment - - edited Using Jira 7.12.1 with application links to Confluence 6.3.1, Bitbucket 5.10.1 and Fisheye 4.6.0 we are getting the same warnings. In a AO_..._HEALTH_CHECK_STATUS table we can see that the error logged is "One of your application links is reporting "Network error."

            Mahtab added a comment -

            Looks like now this bug is being tracked under: https://ecosystem.atlassian.net/browse/ATST-923

            Mahtab added a comment - Looks like now this bug is being tracked under: https://ecosystem.atlassian.net/browse/ATST-923

            Ulrich Dreifke added a comment - - edited

            Using Jira 7.12.1 and Confluence 6.11.2 will cause a lot of warnings inside atlassian-jira.log like 

            2018-10-11 13:36:05,159 HealthCheck:thread-2 WARN [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link '3585f6eb-01d4-33ea-a14b-7d9069d00f95'
            2018-10-11 13:36:05,206 HealthCheck:thread-2 WARN [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link '3099af41-80ad-3ea6-af7b-a96a7a7dabd0'
            2018-10-11 13:36:05,237 HealthCheck:thread-2 WARN [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link '15a64236-0e8f-3e67-b25a-72d35c7d44db'

             

            This was after we update to the newest Version. We have no Problems like that before we update from 7.5.0 and Confluence 6.3.3.

            Ulrich Dreifke added a comment - - edited Using Jira 7.12.1 and Confluence 6.11.2 will cause a lot of warnings inside atlassian-jira.log like  2018-10-11 13:36:05,159 HealthCheck:thread-2 WARN [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link '3585f6eb-01d4-33ea-a14b-7d9069d00f95' 2018-10-11 13:36:05,206 HealthCheck:thread-2 WARN [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link '3099af41-80ad-3ea6-af7b-a96a7a7dabd0' 2018-10-11 13:36:05,237 HealthCheck:thread-2 WARN [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link '15a64236-0e8f-3e67-b25a-72d35c7d44db'   This was after we update to the newest Version. We have no Problems like that before we update from 7.5.0 and Confluence 6.3.3.

            Christopher Graff added a comment -

            Using Jira 7.12.1 & Confluence 6.12.0 and are getting the same.

            Christopher Graff added a comment - Using Jira 7.12.1 & Confluence 6.12.0 and are getting the same.

            Deleted Account (Inactive) added a comment -

            we use Jira 7.11 , Confluence 6.11 and a generic Application

            we are affected too.

            I did not found anything in the logfiles

            Deleted Account (Inactive) added a comment - we use Jira 7.11 , Confluence 6.11 and a generic Application we are affected too. I did not found anything in the logfiles

            Mahtab added a comment -

            Jira 7.12 is also affected.

            Mahtab added a comment - Jira 7.12 is also affected.

              Unassigned Unassigned
              jrey Julien Rey
              Affected customers:
              23 This affects my team
              Watchers:
              79 Start watching this issue

                Created:
                Updated:
                Resolved: