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

Adding a second connector to server.xml will result in a false positive missing maxThreads warning in logs

XMLWordPrintable

      Issue Summary

      When adding a second connector to server.xml, during Confluence boot a false positive warning about missing maximum HTTP Thread (maxThreads) value not being configured on both of them, despite it's being correctly set.

      Environment

      • Confluence 6.15.1

      Steps to Reproduce

      1. Modify Confluence server.xml by adding a second connector with unique port
      2. Restart Confluence

      Expected Results

      • Confluence booth and operates without any issues

      Actual Results

      • Confluence boots and works, but logs a false positive warning in atlassian.confluence.log 
         
2019-03-29 14:06:40,518 WARN [localhost-startStop-1] [confluence.impl.health.DefaultHealthCheckRunner] logEvent Your maximum HTTP Thread size is not configured. The recommended minimum size is 48.
2019-03-29 14:06:40,518 WARN [localhost-startStop-1] [confluence.impl.health.DefaultHealthCheckRunner] logEvent Your maximum HTTP Thread size is not configured. The recommended minimum size is 48.

        Notes

      • We also see on the UI a warning like the following when starting Confluence for the first time after upgrade:

      • maxThreads value is set correctly on both connectors

      Workaround

      • The issue is cosmetic and warning can be ignored
      • Disabling/uncommenting second connector will stop the warning

            [CONFSERVER-58097] Adding a second connector to server.xml will result in a false positive missing maxThreads warning in logs

            Jiri Hronik added a comment -

            A fix for this issue is available to Server and Data Center customers in Confluence 7.13.0
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            Jiri Hronik added a comment - A fix for this issue is available to Server and Data Center customers in Confluence 7.13.0 Upgrade now or check out the Release Notes to see what other issues are resolved.

            Jiri Hronik added a comment - - edited

            A fix for this issue is available to Server and Data Center customers in Confluence 7.12.3
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            Jiri Hronik added a comment - - edited A fix for this issue is available to Server and Data Center customers in Confluence 7.12.3 Upgrade now or check out the Release Notes to see what other issues are resolved.

            Matt Hodges added a comment - - edited

            Having this issue trying to upgrade to 7.11.1 or 7.11.2 - haven't tried older releases.  Currently running 7.7.3. We use two Tomcat connectors - 1 for https and and another for http redirection.

            For us, this is not a cosmetic issue - we have no option to ignore the warning and proceed.  Had the roll back the upgrade and found this post.

            Matt Hodges added a comment - - edited Having this issue trying to upgrade to 7.11.1 or 7.11.2 - haven't tried older releases.  Currently running 7.7.3. We use two Tomcat connectors - 1 for https and and another for http redirection. For us, this is not a cosmetic issue - we have no option to ignore the warning and proceed.  Had the roll back the upgrade and found this post.

            Raghavendra Amara added a comment -

            v7.4.5

            Raghavendra Amara added a comment - v7.4.5

            Balázs Lengyák added a comment -

            v7.4.8 too

            Balázs Lengyák added a comment - v7.4.8 too

            Allan Buck added a comment -

            Same issue on 7.11.1 as well....

            Allan Buck added a comment - Same issue on 7.11.1 as well....

            Tommy van Extel added a comment -

            Same issue on 7.10.2

            Tommy van Extel added a comment - Same issue on 7.10.2

            Vignesh Kumar added a comment -

            Is the ETA on this ? We are facing this issue on 7.4.3. 

            Vignesh Kumar added a comment - Is the ETA on this ? We are facing this issue on 7.4.3. 

            Lindsey Dengler added a comment -

            Fix this please. This is causing us production outages as we have to restart confluence at least once a week to solve for other performance issues. 

            Lindsey Dengler added a comment - Fix this please. This is causing us production outages as we have to restart confluence at least once a week to solve for other performance issues. 

            Gonchik Tsymzhitov added a comment -

            It will be good to update the KB about false positive  

            Gonchik Tsymzhitov added a comment - It will be good to update the KB about false positive  

              oshen@atlassian.com Oliver Shen
              imuzaliov Igor M.
              Affected customers:
              50 This affects my team
              Watchers:
              58 Start watching this issue

                Created:
                Updated:
                Resolved: