Confluence : Release Notes 1.4.2
This page last changed on Jun 29, 2006 by david.soul@atlassian.com.
Confluence 1.4.2 is a maintenance release that resolves some issues users may have encountered using previous Confluence 1.4 releases. 1.4.2 introduces Websphere and DB2 compatibility, and fixes issues related to content indexing and the mail queue. 1.4.2 is a free upgrade for all customers who purchased their Confluence license after June 30th, 2004. Who should upgrade?Confluence 1.4.2 is a bugfix release. Customers should consult the list of issues resolved for this release to decide whether it is worth their while upgrading. Since this release includes a number of important performance and reliability fixes for content indexing, anyone who relies on Confluence's search functionality should consider upgrading. Upgrade ProcedureUpgrading Confluence should be pretty easy. If you are upgrading from Confluence 1.4 or 1.4.1, you can find instructions here. We strongly recommend that you backup your confluence.home directory and database before upgrading! If you are upgrading from Confluence 1.3.6 or earlier, be sure to read the upgrade instructions in the Confluence 1.4 release notes. Database Connection Pool ChangesDependent on the size of your Confluence installation, the new re-indexing task may use up to 10 database connections simultaneously. As such, you may need to increase the size of your database connection pool in order to allow Confluence to continue to operate during and after rebuilding the search index. If Confluence has been set up to use direct JDBC connections, then you will find the setting for Confluence's connection pool size in confluence.cfg.xml in your confluence home directory. Confluence should update this value automatically when you upgrade, so after starting up Confluence 1.4.2 for the first time, you should check to make sure it has been updated to 15 connections, as seen below: <property name="hibernate.c3p0.max_size">15</property> If Confluence has been configured to use a datasource supplied by the application server, you should ensure the application server is configured to supply Confluence with sufficient connections to run. Changes in 1.4.2See also: Issues Resolved for 1.4.2
|
![]() |
Document generated by Confluence on May 01, 2007 19:28 |