Confluence 3.1.1 Release Notes
27 January 2010Confluence 3.1.1 is a recommended upgrade which fixes a number of issues.
Performance Enhancements and Fixes
This release fixes two bugs that affected configuration of Confluence's internal caches. The first bug caused an error to be thrown when a Confluence internal cache was either increased to over 5000 elements (from under 5000) or resized when it was already over 5000 elements, via the Administration Console. The second bug caused changes made to Confluence's internal caches via the Administration Console to be lost after a Confluence restart. This meant that caches could only be resized by manually editing the cache configuration files (XML).
We identified an issue where Hibernate was not cleaning up its session correctly when closed, causing memory leaks. We have changed the way that Hibernate SessionImpl objects are stored which should fix this problem and reduce memory consumption.
A system property (atlassian.user.experimentalMapping) was introduced in Confluence 2.10 to fix performance problems noted when adding a local user to a local user group. We have fixed an bug with this system property that prevented users from being removed from user groups via the Administration Console, when the system property is set.
Other Fixes
We have found a bug that periodically caused an error to display when trying to view the 'Confluence Gadgets' window. This has now been fixed.
There's a complete list of fixes below. Click a specific issue to see details of the fix.Don't have Confluence 3.1 yet?
Take a look at the new features and other highlights in the Confluence 3.1 Release Notes.
Upgrading from a Previous Version of Confluence
Upgrading Confluence should be fairly straightforward. Please read the Confluence 3.1.1 Upgrade Notes. We strongly recommend that you back up your confluence.home directory and database before upgrading.
Updates and Fixes in this Release
| type | key | summary | priority | status | resolution |
|---|---|---|---|---|---|
|
Data cannot be retrieved due to an unexpected error. View these issues in Jira |
|||||
If you like, you can open a report on jira.atlassian.com showing all resolved and closed issues in this release.