Confluence 7.10 Upgrade Notes
Here are some important notes on upgrading to Confluence 7.10. For details of the new features and improvements in this release, see the Confluence 7.10 Release Notes.
On this page:
Managed Synchrony memory increase
The default maximum heap size (Xmx) allocated to Synchrony has been increased from 1 GB to 2 GB, so you may need to increase the memory available to Confluence. You can change this default using the
synchrony.memory.max system property.
In this release we upgraded the version of Xstream bundled with Confluence. This is a major upgrade that may have an impact on custom apps you may have developed.
See XStream 1.4 upgrade for full details.
You may find that some Marketplace apps are not compatible with Confluence 7.10 on release day. We recommend upgrading Confluence in a test environment, and checking that all your apps start up and work as expected, so you don't get any surprises when you upgrade. If you do find an app doesn't start up, contact the app vendor for assistance.
PostgreSQL driver upgrade
We've upgraded the PostgreSQL driver bundled with Confluence from 42.2.6 to 42.2.16. We don't expect there to be any impact. See the PostgreSQL JDBC driver changelog if you want more details.
Login with query parameter no longer supported
From Confluence 7.10 we will prevent you from using the
os_username+os_password query parameter to log in.
If you have any custom integrations that use this method, you should switch to basic authentication, or consider a more secure option, such as personal access tokens.
If you need more time to update your integrations, you can set the
atlassian.allow.insecure.url.parameter.login system property to
true as a workaround.
End of support announcements
No end of support announcements at this time.
Head to Preparing for Confluence 7.10 to find out more about changes under the hood.
There's a known issue running PostgreSQL on Azure with the bundled version of the driver (42.2.16). See CONFSERVER-60515 for a workaround
If you are upgrading from Confluence 6.3 or earlier, there's a known issue where spaces do not appear in the space directory. You'll need to reindex your site after upgrading to fix this.
- If you use Apache to limit who can access the admin console, you should update your configuration. See Using Apache to limit access to the Confluence administration interface for our suggested configuration.
- There is a known issue where read-only mode attempts to write to
<shared-home>/confluence.cfg.xml, but the file doesn't exist in the shared home directory. This problem affects sites that have been previously upgraded from Confluence 6.0 or earlier. See Could not save access.mode into the shared confluence.cfg.xml file error after upgrading to Confluence Data Center 6.10
- There is a known issue where some fonts that Confluence relies on are not available in older Linux distributions. See Confluence UI shows garbled or corrupt text on CAPTCHA, macros and/or diagrams due to missing fonts.
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.
Always test the upgrade in a test environment before upgrading in production.
To upgrade Confluence to the latest version:
- Go to > Plan your upgrade and select the version you want to upgrade to. This will run the > General Configurationpre-upgrade checks.
- Go to > Troubleshooting and support tools > General Configuration to check your license validity, application server, database setup and more.
- If your version of Confluence is more than one version behind, read the for all releases between your version and the latest version.
- Back up your installation directory, home directory and database.
- Download the latest version of Confluence.
- Follow the instructions in the Upgrade Guide.
Update configuration files after upgrading
The contents of configuration files such as
server.xml, web.xml ,
confluenceinit.properties change from time to time.
When upgrading, we recommend manually reapplying any additions to these files (such as proxy configuration, datasource, JVM parameters) rather than simply overwriting the file with the file from your previous installation, otherwise you will miss out on any improvements we have made.