Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-45506

EOL Check Causes Health Check to Fail when a proxy is being used

    XMLWordPrintable

Details

    Description

      Note : This is a bug cloned from JRA-61781

      Health Check Results :

      Name: End Of Life
      Is healthy: false
      Failure reason: TimeoutException after 20000ms
      Severity: UNDEFINED
      

      Looking at the logs, you should expect the following error while Confluence is running EOL Health Check :

      2016-11-10 10:01:17,231 ERROR [SupportHealthCheckThread-8] [plugins.healthcheck.eol.EolSupportHealthCheck] check An error occurred when performing the EOL check, see the exceptions for more info
      org.apache.http.conn.ConnectTimeoutException: Connect to marketplace.atlassian.com:443 [marketplace.atlassian.com/131.103.28.7] failed: Connection timed out
      	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:149)
      	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
      	at org.apache.http.impl.execchain.MinimalClientExec.execute(MinimalClientExec.java:183)
      	at org.apache.http.impl.client.MinimalHttpClient.doExecute(MinimalHttpClient.java:107)
      	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
      	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
      	at com.atlassian.confluence.plugins.healthcheck.util.SupportEolCheckUtil.makeRequestToMarketplace
      
      Workaround

      Create <CONFLUENCE_HOME>/shared-home/confluence-healthcheck-eol.json with example content. This file is located in the /var/atlassian/application-data/shared-home folder by default on a linux system.

      {"versions":[{"name":"5.9","releaseDate":"2015-11-24"},{"name":"5.10","releaseDate":"2016-06-09"},{"name":"6.8","releaseDate":"2018-03-19"},{"name":"6.9","releaseDate":"2018-05-07"},{"name":"6.10","releaseDate":"2018-06-25"},{"name":"6.0","releaseDate":"2016-10-31"},{"name":"6.1","releaseDate":"2017-03-16"},{"name":"6.2","releaseDate":"2017-05-12"},{"name":"6.3","releaseDate":"2017-07-06"},{"name":"6.4","releaseDate":"2017-09-05"},{"name":"6.5","releaseDate":"2017-11-01"},{"name":"6.6","releaseDate":"2017-12-11"},{"name":"5.8","releaseDate":"2015-06-02"},{"name":"6.7","releaseDate":"2018-01-29"}]}
      
      Notes

      The issue also seems to be happening on environment that utilize outbound proxy, whereby, even configuration are done correctly (adding marketplace to the non proxy host config), and connection towards Marketplace is possible (add-ons and UPM works fine), the healthcheck plugin still throws Connect to marketplace.atlassian.com:443 [marketplace.atlassian.com/131.103.28.7] failed: Connection timed out

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jwaihou Jonathan Soo
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: