Confluence 5.10 Upgrade Notes
Below are some important notes on upgrading to Confluence 5.10. For details of the new features and improvements in this release, see the Confluence 5.10 Release Notes.
Favorite pages is now Saved for later
We've renamed the Favorite pages feature to Saved for later. This is just a name change; the essential behavior of this feature hasn't changed.
Changes to keyboard shortcuts
We've made some changes to how keyboard shortcuts are bound in the editor:
- Mac users can no longer use Control or Command interchangeably for some keyboard shortcuts in the editor. It's ⌘ all the way from now on.
- Mac users can now use Control-E to jump to the end of a line in the editor.
- Safari users can now use Command-Control-0 to 9 to change the heading style.
Application links authentication changes
It's no longer possible to configure an application link to use Trusted Application or Basic Access authentication.
Existing application links will continue to work for now, but you will be prompted to upgrade these to use the industry standard OAuth authorization protocol. See OAuth security for application links for more information on how to update existing application links.
XSS protection for plugins
It is no longer possible to turn off Anti XSS Mode for plugins, so the option has been removed from the Security Configuration screen. Anti XSS mode has been enabled by default since Confluence 3. If you have previously turned off Anti XSS Mode for plugins, it will be turned on automatically when you upgrade to Confluence 5.10.
Changes to database connection pool and HTTP thread settings
We've made some changes to the recommended size of the database connection pool and maximum number of HTTP threads. These changes help keep Confluence stable, especially under high load.
The default values for new instances are:
|Current value||Recommended value|
|Maximum database connections||30||60|
|Minimum database connections||0||20|
|Maximum HTTP threads||200||48|
During the upgrade your maximum HTTP threads will be reduced from 200 to 48. Your current database connection pool settings will not change, but you may want to adjust your database connection pool settings in line with our defaults.
<confluence-installation>/conf/server.xml and change
maxThreads to your desired value.
<Service name="Tomcat-Standalone"> <Connector port="8090" connectionTimeout="20000" redirectPort="8443" maxThreads="48" minSpareThreads="10" ...
Before making this change, you should check that the total size of the connection pool does not exceed the number of connections allowed by your database (for Data Center, this means the database must allow enough connections to cater for the maximum database connections value for all nodes combined).
The method for updating the connection pool settings depends on how your database connection is configured.
If you have a direct JDBC connection, go to
<confluence-home>confluence.cfg.xmland edit the following properties:
<property name="hibernate.c3p0.max_size">60</property> ... <property name="hibernate.c3p0.min_size">20</property>
If you have a datasource connection, go to
<installation-directory>/conf/server.xmland update the following in your datasource resource.
... maxTotal="60" maxIdle="20" ...
Head to Preparing for Confluence 5.10 to find out about changes that will impact plugin developers.
Supported platform changes
In this release we've added support for:
- Microsoft Edge
- PostgreSQL 9.4 and 9.5
End of support announcements
- Advance notice: end of support for Internet Explorer 10
Confluence 5.10.x will be the last release to support Internet Explorer 10. See announcement.
- Advance notice: end of support for MySQL 5.5
Confluence 5.10.x will be the last release to support MySQL 5.5. See announcement.
- Advance notice: changes to Confluence distributions
To help us bring you new Confluence Server versions faster, we are considering only providing 64-bit installers. Confluence 5.10 would be the last Confluence release to provide a 32-bit installer. See announcement.
- Advance notice: Documentation theme
As previously announced, we plan to remove the documentation theme in Confluence 6.0. The documentation theme is still available in Confluence 5.10 but we encourage you to give the default theme a try now, to make your move to Confluence 6.0 easier.
- Advance notice: View File macros
As previously announced, we have officially deprecated the View File macros (Office Word, Office PowerPoint, Office Excel, and PDF). These macros are still available in Confluence 5.10. We have not yet determined when they will be removed, and will provide plenty of notice when the time comes.
- Upgrading from 6.0.0-OD-x to 5.10 RESOLVED
If you have migrated from Confluence Cloud to Confluence Server in the last few months, and are running a 6.0.0-OD version of Confluence, you won't be able to use the installer to upgrade to Confluence 5.10.0. The earliest version you'll be able to upgrade to is 5.10.4.
Note: Upgrade to a test environment first. Test your upgrades in your test environment before rolling them into production.
If you're already running a version of Confluence, please follow these instructions to upgrade to the latest version:
- Go to > General Configuration > Support Tools > Health Check to check your license validity, application server, database setup and more.
- Before you upgrade, we strongly recommend that you back up your installation directory, home directory and database.
- If your version of Confluence is earlier than 5.8, read the release notes and upgrade guides for all releases between your version and the latest version.
- Download the latest version of Confluence.
- Follow the instructions in the Upgrade Guide.
Checking for known issues and troubleshooting the Confluence upgrade
After you have completed the steps required to upgrade your Confluence installation, check all the items on the Confluence post-upgrade checklist to ensure that everything works as expected. If something is not working correctly, please check for known Confluence issues and try troubleshooting your upgrade as described below:
- Check for known issues. Sometimes we find out about a problem with the latest version of Confluence after we have released the software. In such cases we publish information about the known issues in the Confluence Knowledge Base.
- Check for answers from the community. Other users may have encountered the same issue. You can check for answers from the community at Atlassian Answers.
- Did you encounter a problem during the Confluence upgrade? Please refer to the guide to troubleshooting upgrades in the Confluence Knowledge Base.
- If you encounter a problem during the upgrade and can't solve it, please create a support ticket and one of our support engineers will help you.
Was this helpful?Yes Provide feedback about this article