The 5.7 branch of Magnolia reached End-of-Life on December 31, 2023, as specified in our End-of-life policy. This means the 5.7 branch is no longer maintained or supported. Please upgrade to the latest Magnolia release. By upgrading, you will get the latest release of Magnolia featuring significant improvements to the author and developer experience. For a successful upgrade, please consult our Magnolia 6.2 documentation. If you need help, please contact info@magnolia-cms.com.
H2 does not accept more than one connection
Our default configuration does not use server mode. Therefore, if you try to initiate a backup call using CLI or REST, it fails because H2 does not allow more than one connection at a time. This is a new issue in Magnolia (most likely due to H2 or Jackrabbit updates).
A temporary workaround is to make H2 run in server mode and adding AUTO_SERVER=TRUE
in the URL parameters:
<param name="url" value="jdbc:h2:${wsp.home}/db;AUTO_SERVER=TRUE" />
<param name="url" value="jdbc:h2:${rep.home}/version/db;AUTO_SERVER=TRUE" />
See MAGNOLIA-7227 - Getting issue details... STATUS
Reloading a page in the editor causes a 404 error
When you open a page for editing and reload it in the browser, an extra semicolon is added to the URL fragment and the server returns a 404 error. Every subsequent reload adds another semicolon. This issue occurs with older versions of the Tomcat application server. To resolve this issue, upgrade to Tomcat 7.0.47+. See MGNLUI-2426 - Getting issue details... STATUS
Tomcat 7.0.66+ Trailing slash issue
When accessing the webapp without the trailing slash after the context http://localhost:8080/magnoliaAuthor after login the user is presented with a 404 page rather than admincentral. This behavior is configurable via the mapperContextRootRedirectEnabled
and mapperDirectoryRedirectEnabled
attributes of the Context which may be used to restore the previous behavior. See Apache Tomcat 7 Changelog.
Oracle WebLogic 10 conflict with commons-lang library
When deploying on Oracle WebLogic 10, there is a version conflict while using commons-lang
. While Oracle WebLogic-10 is distributed with commons-lang-2.3.jar
, JackRabbit and Magnolia need at least commons-lang-2.4.jar
. To resolve this issue, modify setDomainEnv.sh
of Oracle WebLogic and add commons-lang-2.4.jar
to the PRE_CLASSPATH
. Since version 2.4 commons-lang
doesn't remove any methods, but only adds new API and fixes known bugs, there is no adverse effect from this change to the Oracle WebLogic installation.
Oracle WebLogic 12c conflict with Bouncy Castle library
Magnolia uses the Bouncy Castle cryptography package to decode the license key and to secure the activation process. Oracle WebLogic 12c is distributed with bcprov-jdk16-1.45.jar
but Magnolia is distributed with bcprov-jdk16-1.46.jar
. This leads to a library version conflict.
Symptom: after inserting valid license key into the Magnolia license form, the error message "License is empty" is displayed.
To resolve, do one of the following:
- Edit
setDomainEnv.sh
in Oracle WebLogic and addbcprov-jdk16-1.46.jar
toPRE_CLASSPATH
or - Remove
bcprov-jdk16-1.45.jar
from Oracle WebLogic 12c common libraries.
Oracle WebLogic and IBM WebSphere deployment issue with jBPM 6
jBPM 6 cannot be deployed on Oracle WebLogic or IBM WebSphere. jBPM is included in the Magnolia Workflow module. All deployment methods are affected: Administration Console, Oracle WebLogic.Deployer, wldeploy Ant task and autodeploy directory.
Symptom:
weblogic.application.ModuleException: java.lang.ClassNotFoundException: org.jbpm.services.task.lifecycle.listeners.TaskLifeCycleEventListener
Workaround:
- Deploy an application which doesn't contain Magnolia Workflow with jBPM6, for example Magnolia 5.2.2 or Magnolia 5.3 without the Workflow module.
- In the deployment target location, replace the deployed webapp with a new webapp that contains workflow with jBPM6
Oracle WebLogic 12c conflict with Google Guava library
Magnolia cannot render images stored in dam
workspace. Google Guava library is used by the DAM API 2.0 which is used for working with images.
Symptom:
java.lang.RuntimeException: java.lang.NoClassDefFoundError: Could not initialize class com.google.common.cache.LocalCache
Workaround:
Modify the weblogic.xml
file in your application's WEB-INF
folder with the prefer-application-packages
element:
<container-descriptor> <prefer-application-packages> <package-name>com.google.common.*</package-name> </prefer-application-packages> </container-descriptor>
Jetty 9± java.io.IOException
stream closed
Magnolia's resource loader makes heavy use of accessing classpath resources (last modification date and contents). Jetty uses caching of such resources by default, which may result in a java.io.IOException
occurring randomly. See
MAGNOLIA-6860
-
Getting issue details...
STATUS
.
Mac OS X 10.5 - Leopard
If you use Mac OS X 10.5 or 10.6, you should update to at least 10.5.8 or 10.6.2. Earlier versions cause issues where, when two or more instances are started in the same container, some or all connections are dropped.
The symptoms are that Tomcat is unreachable ("kCFErrorDomainCFNetwork:302") but no log message clearly identifies the issue. Sometimes pages can be loaded but resources cannot, leading to missing images or stylesheets. Another symptom is that you have to kill the Tomcat process to stop it (-HUP works) because the shutdown script cannot reach the running process either. See MAGNOLIA-1959 for more details and comment on your own experience.
Too many open files
The embedded Derby database that Magnolia uses for demonstration opens several file handles and may run over the maximum limit set by the system. This issue can occur on some Linux and OS X systems such as Macbook Air.
The solution is to increase the system-wide limit on the number of open files. The exact procedure varies from one OS to the next, see Too many open files.
Session de-serialization
When installing or updating to a new version, you may see this error message:
2009-11-24 13:02:14,970 ERROR org.apache.catalina.session.ManagerBase : IOException while loading persisted sessions
This can be due to changes in signatures of classes that are stored in user sessions, such as permissions, user, etc. The error happens when Tomcat attempts to de-serialize serialized sessions as the container starts. The de-serialization causes the loss of persisted sessions. Users will have to log in again. Otherwise it is a harmless error and can be ignored.
Xalan
If you see the following error message in your logs:
javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
Add the Xalan jar to the WEB-INF/lib
folder of your Magnolia instances, delete the repositories and start again. Please see MAGNOLIA-1958 for more details and comment on your own experience.
Port 8080 is already in use
Port 8080 is the default port for Tomcat. You can see it at the end of the default address http://localhost:8080
. If another application on the computer is already using the same port you may need to change it.
- Open
<CATALINA_HOME>/conf/server.xml
in a text editor. This file is under your Magnolia installation directory. Find the following section and set the value of
port
to something other than 8080, for example 8090:<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 --> <Connector port="8090" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" />
Change the defaultBaseUrl
property which is used to generate links in emails or other external systems. To do this, you need to now access Magnolia at the new port 8090.
- Log into the author instance at
http://localhost:8090/magnoliaAuthor/.magnolia
. - Go to Configuration.
- Set the value of
/server/defaultBaseUrl
property tohttp://localhost:8090/magnolia/
. - Log into the public instance at
http://localhost:8090/magnoliaPublic/.magnolia
. - Go to Configuration.
- Set the value of
/server/defaultBaseUrl
property tohttp://localhost:8090/magnolia/
.
Now the Welcome page at
http://localhost:8090
has the correct URLs too.
The port also needs to be changed in publishing configuration, otherwise publishing (activating) changes from the author to public instance fails.
- On the author instance,
- If you are using the Publishing module, go to Configuration > modules > publishing-core > config > receivers .
- If you are using the Activation module, go to Configuration > modules > activation > subscribers .
- Under the
magnoliaPublic8080
receiver (subscriber), set theURL
property tohttp://localhost:8090/magnoliaPublic
. - Rename the receiver (subscriber) to
magnoliaPublic8090
. - Activate the modified receiver (subscriber) including its subnodes.
If you want to run two different Tomcats simultaneously you need to change other ports too. This is useful if you want to run different versions of Magnolia at the same time. In <CATALINA_HOME>/conf/server.xml
, change the port numbers for the shutdown and AJP sections and any custom sections you have enabled.
Windows Firewall is blocking Java
Allow an exception in Windows Firewall for Java.
- Go to Control Panel > Windows Firewall.
- Go to the Exceptions tab.
- Click Add Program and browse to the java.exe file in the Java installation directory, for example
C:\Sun\SDK\jdk\bin\java.exe
. - Click OK.
If you get a security alert during startup, check the Private networks checkbox and click Allow access.
CATALINA_HOME environment variable is not defined
CATALINA_HOME environment variable identifies the Tomcat home directory, for example C:\Program Files\magnolia\apache-tomcat
. Usually Magnolia finds this directory automatically. When you type magnolia_control.bat start
in the bin
directory to start the system, a second script named startup.bat
tries to find Tomcat home. It assumes that Tomcat home is one level above the bin
directory where you issued the command, and sets the value of CATALINA_HOME to that directory.
C:\Program Files magnolia apache-tomcat <-- Tomcat home directory bin <-- magnolia_control.bat is here
However, if you added the bin
directory to your PATH environment variable you can execute magnolia_control.bat
from anywhere. This means startup.bat
does not find Tomcat home directory by simply moving up one level from where you are and displays the following error:
To correct this define CATALINA_HOME in environment variables. Follow the instructions in Set JAVA_HOME environment variable.
Java out of memory
If the Java Virtual Machine (JVM) does not have enough memory you may see a
java.lang.OutOfMemoryError
in the startup log and Magnolia fails to start.
Exception in thread "Timer-1" java.lang.OutOfMemoryError: Java heap space at org.apache.jackrabbit.core.query.lucene.IndexingQueue.getFinishedDocuments
Increase Java heap size to allocate more memory to JVM:
- Stop the server.
./magnolia_control.sh stop
- Open file
/apache-tomcat/bin/setenv.sh
(/apache-tomcat/bin/setenv.bat
on Windows) in a text editor. - Edit the
Xmx
parameter to set a new maximum heap size. Default size for Magnolia is 512M, try a higher amount such as 1024M. - Save the file and start the server.
./magnolia_control.sh start && tail -f ../logs/catalina.out
JAR file does not start
When installing the Enterprise Edition on Windows, you can start the installer by double-clicking the JAR file. If this does not work there is a chance that some application on your system has registered the .jar extension.
You can try to fix it yourself by restoring the association of the .jar extension with the javaw.exe
executable. .Right-click the JAR file and select Open With. Typically the javaw.exe
file is in C:\Program Files (x86)\java\jre6\bin
). Alternatively, start the installer from a command prompt with the following command: java -jar magnolia-enterprise-installer-x.y.z.jar
. Make sure the file extension is .jar. Internet Explorer has a tendency to append or change it to .zip.
Activation errors
For issues related to activation keys and the handshaking process, see the Activation errors page.