Confluence 5.5.1-m2 EAP リリースノート
Atlassian is pleased to announce Confluence 5.5.1 milestone 2 (m2). This is the fourth public milestone release of Confluence 5.5 and provides a snapshot of our continued work on Confluence's clustering solution.
Note: A standalone artifact will not be provided for this milestone.
This EAP (early access program) release is a snapshot of our work in progress, primarily focused on giving plugin developers an opportunity to test and fix their plugins in advance of an official release. Feel free to comment on the page if you want to provide any feedback or ask any questions.
Development releases are not production ready. Development releases are snapshots of the ongoing Confluence development process. While we try to keep these releases stable, they have not undergone the same degree of testing as a full release, and could contain features that are incomplete or may change or be removed before the next full release.
No upgrade path. Because development releases represent work in progress, we cannot provide a supported upgrade path between development releases, or from any development release to a final release. You may not be able to migrate any data you store in a Confluence development release to a future Confluence release.
Atlassian does not provide support for development releases.
Highlights of this release
This milestone contains a snapshot of our work on Confluence's clustering solution and is provided to allow plugin developers time to ensure their plugins are cluster compatible ahead of Confluence 5.6. See Starting a Confluence cluster on a single machine for information on how to set up an environment for testing purposes.
Note that Confluence 5.5 does not include a clustered artifact, and customers wishing to set up a cluster in production will need to continue to use Confluence 5.4. We hope to make the new Confluence clustering solution available with Confluence 5.6.
This release contains a number of bug fixes and improvements including:
- Upgrade to Hazelcast 3.2.1.
- Performance improvements to reduce the cache traffic load on the network.
It also contains all the new Confluence 5.5 features.
Note for plugin developers: Do not assume that caching is cheap in a clustered environment (as is the case for stand-alone Confluence). Each operation on a Clustered cache may involve a network call and will definitely involve object serialization. If possible, caches should be made local. Also, consideration should be given to using the
com.atlassian.confluence.cache.ThreadLocalCacheAccessor class to provide per-request caching.
We'd love your feedback so please:
- Feel free to comment on this page with your feedback, or
- Send us your comments via the 'Got Feedback' option in the header of your EAP Confluence site.
For clustered installations the following extra steps apply. (These extra steps do not apply if you have previously upgraded to one of the Confluence 5.5 milestones).
Follow the normal upgrade procedure, but execute the following steps immediately after shutting down the existing cluster:
- Create a directory that is visible to all cluster nodes in the same path.
- Shut down the cluster.
confluence.cfg.xmlin the home directory of each node and add a new property called
confluence.cluster.homewith the path of the shared directory as the value. Example:
- Move all the files/directories from a home directory on one node to the new shared home directory except for the following:
- Remove the moved files/directories from the home directories on all other nodes.
- Continue to follow the normal upgrade procedure.