Details
-
Bug
-
Resolution: Fixed
-
Highest
-
6.15.1, 6.15.2, 6.15.4, 7.0.1, 7.1.0, 7.3.5, 7.4.0, 7.4.1, 7.4.7, 7.4.8
-
72
-
Severity 3 - Minor
-
126
-
Description
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
- Modify Confluence server.xml by adding a second connector with unique port
- 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
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
PS-63053 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-