Confluence does not boot with getHttpConnector Expected exactly one HTTP connector in Tomcat configuration
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Confluence is failing to boot with last entry in atlassian-confluence.log being this
WARN [StartEventPublisher:thread-1] [impl.util.tomcat.DefaultTomcatConfigHelper] getHttpConnector Expected exactly one HTTP connector in Tomcat configuration, but found []Cause
Confluence Tomcat configuration change might have been implemented incorrectly, such as proxy addition or connector change.
If Confluence is booting correctly, but the error persists, Confluence might be affected by false positive CONFSERVER-58739 - Configuring the Tomcat connector with a protocol different from NIO might cause a false warning about maximum HTTP thread size bug.
Solution
Review tomcat configuration file to make sure syntax is correct.
- Verify
<confluence-install-directory>/conf/server.xml- Check that all unused connectors or reference notes are properly closed where applicable (using <!-- & --> symbols)
- Verify that connectors parameters are not missing any quotation marks ("")
- Make sure that you do not have two connectors configured to listen on the same port
- Restore server.xml file to previous working version from backup