Release notes for Magnolia 4.4.9
- What has changed since Magnolia CMS 4.4.8
- Should you upgrade?
- How to update from Magnolia CMS 4.4.8, 4.4.7, 4.4.6, 4.4.5, 4.4.4, 4.4.3, 4.4.2, 4.4.1 or 4.4
- How to update from Magnolia 4.3.8
- Known issues
What has changed since Magnolia CMS 4.4.8
Magnolia CMS 4.4.9 is a maintenance release that includes Jackrabbit 2.4, the latest version of the JCR repository implementation. Jackrabbit 1.6 is no longer supported by the Apache Software Foundation. Jackrabbit 2.4 brings some fixes that benefit larger Magnolia CMS installations.
To reflect this change, Maven artifacts use version
This release includes the following new module versions:
- Magnolia 4.4.9 (CE)
- Magnolia Enterprise Edition 4.4.9 (EE)
- Magnolia Diff Module 1.0.6 (EE)
- Magnolia XA Activation (exchange-transactional) 1.2.4 (EE)
Should you upgrade?
When we release a new major version we continue to support the previous major version for another two years. This means that you don't have to upgrade Magnolia CMS or the Jackrabbit repository every time we release. However, if you run into problems with an unsupported version of Jackrabbit we may ask you to upgrade to a newer version.
- If your website has high load and multiple threads request the same piece of content at the same time, you might run into a situation where the threads get interlocked. Any future requests for that same content will get locked as well. In Jackrabbit 1.6 the only way to resolve the lock and release the threads is to restart the server. In Jackrabbit 2.0 this issue is solved by allowing multiple threads to fetch the same content into the cache and override the cached entry. The probability that you will run into this issue is low. However, if the problem on your site is caused by infrastructure rather than the number of incoming requests, you are likely to run into it over and over again. If your server stops responding, you do a thread dump, and discover that threads are blocked in the shared item cache then consider upgrading.
- If you have a Magnolia CMS cluster, you may see cluster configuration issues similar to thread locking. These were fixed between Jackrabbit 1.6 and 2.4.
- If you have a lot of binary content (PDF, Word) that needs to be indexed for search, consider upgrading. With Jackrabbit 1.6 the search index can get corrupted when you upload a corrupted PDF file into the DMS workspace. Indexing of binary content was greatly improved in Jackrabbit 2.4.
How to update from Magnolia CMS 4.4.8, 4.4.7, 4.4.6, 4.4.5, 4.4.4, 4.4.3, 4.4.2, 4.4.1 or 4.4
Please refer to the general update procedure page.
How to update from Magnolia 4.3.8
Since Magnolia 4.4, requests are dispatched to the main filter also on includes (MAGNOLIA-3338): you have to update your
<filter-mapping> <filter-name>magnoliaFilterChain</filter-name> <url-pattern>/*</url-pattern> <dispatcher>REQUEST</dispatcher> <dispatcher>FORWARD</dispatcher> <!-- add the following line: --> <dispatcher>INCLUDE</dispatcher> <dispatcher>ERROR</dispatcher> </filter-mapping>
Please see the release notes pages for update instructions specific to each version following the version you are updating from; if you're updating from a fictional 1.2.3 to 1.2.6, for example, please read all release notes concerning the versions you are skipping (1.2.4 and 1.2.5 in this example).
JBoss 5There is an unfortunate issue, specifically when deploying under JBoss 5: you will need to remove the Xerces jar from the Magnolia CMS webapps: if deploying using WAR files, you can remove it from the archive, or with the following Unix command
zip -d path-to-magnolia.war WEB-INF/lib/xercesImpl-2.8.1.jar. If deploying using an exploded directory, simply remove the
WEB-INF/lib/xercesImpl-2.8.1.jarfile. See MAGNOLIA-2577 for technical details. If you get exception messages such as
org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parserand/or
java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration, this is the issue you're hitting.
Weblogic 10When deploying on Weblogic 10, there is a version conflict while using
commons-lang. While Weblogic-10 is distributed with
commons-lang-2.3.jar, JackRabbit and Magnolia CMS need at least
commons-lang-2.4.jar. To resolve this issue, modify
setDomainEnv.shof Weblogic and add
PRE_CLASSPATH. Since version 2.4 of
commons-langdoesn't remove any methods, but only adds new API and fixes known bugs, there is no adverse effect from this change to the Weblogic installation.
Weblogic 9The imaging module doesn't function properly due to conflict with a
javax.imageioplugin bundled with this version of Weblogic. There is currently no known workaround for the issue. Please see the list of known issues in the administration section for more details.