Issue Summary

Bamboo version 12 and 12.1 bundle Tomcat 10, which has changes to the way certain arguments are declared:

https://confluence.atlassian.com/bambooreleases/bamboo-12-0-upgrade-notes-1671463218.html#Bamboo12.0upgradenotes-Spring,Jakarta,andTomcatupgrades 

This requires users upgrading Bamboo who have custom server configurations or connectors to review the following before upgrading:

• Check any custom server.xml }}settings, especially those referencing the {{javax.servlet APIs, as Tomcat 10.1 now uses the jakarta.servlet namespace.
• Ensure all connectors (such as HTTP or AJP) are compatible and properly configured for Tomcat 10.1.
• Verify that your security and TLS/SSL settings work with the updated cryptographic defaults in Tomcat 10.1.
• For a full list of changes and guidance, see the official Apache Tomcat 10.1 documentation.

Steps to Reproduce

Upgrade Bamboo from any older version to 12.0 or 12.1, using custom server.xml settings (like keystore, certificates, etc).

Expected Results

Since this is a major change in Tomcat for customers with custom server.xml settings, the upgrade guide should mention that.

Actual Results

If customers are upgrading Bamboo from versions older than 12 to 12.0 or newer and miss the platform change in the release notes, and they have custom server configurations and connectors, their Bamboo will fail to start until they adjust the syntax to the new Tomcat 10 requirements.

Although the page mentions the need to migrate the server.xml customizations during the upgrade, it does not call out the differences in 12.0 and 12.1. If we simply copy the customizations, they will not work on 12.0 and 12.1 and need to be rewritten using the new syntax/requirements.

Workaround

The customer needs to update their server.xml to the new syntax if using custom settings, as described in the release notes.

Also, this Jira KB might help them with those steps: https://support.atlassian.com/jira/kb/jira-data-center-11-0-x-and-tomcat-10-1-ssl-configuration-guide/

Suggestion/request

We should include a note/warning in the upgrade guide that mentions the Tomcat changes and that they may need to update their server.xml to the new syntax if using custom settings, as described in the release notes.

Also, this Jira KB might help them with those steps: https://support.atlassian.com/jira/kb/jira-data-center-11-0-x-and-tomcat-10-1-ssl-configuration-guide/