Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
These are common issues that you may encounter during system installation or use.
There is an unfortunate issue, specifically when deploying under JBoss 5: you will need to remove the Xerces .jar from the Magnolia 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.jar file. See
org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parseror
java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration, this is the issue you're hitting.
JBoss 7 Application Server adds its own log4j logging configuration. If you want to your own log4j logging configuration in your deployment, you need to exclude the JBoss configuration first.
Create a new file
jboss-deployment-structure.xml under the
WEB-INF folder with this content:
WebLogic 9 also ships with an old version of JDom which later leads to issues in parsing of XML documents. Issues will be noted as exceptions such as:
To resolve, provide newer JDOM/Jaxen libraries by adding
PRE_CLASSPATH variable in the
When 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 need at least
commons-lang-2.4.jar. To resolve this issue, modify
setDomainEnv.sh of 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 Weblogic installation.
Magnolia uses the Bouncy Castle cryptography package to decode the license key and to secure the activation process. 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: there is no error shown on the Magnolia license form but the license is not registered. In the log you can find this stack trace:
To resolve, do one of the following:
setDomainEnv.shin WebLogic and add
bcprov-jdk16-1.45.jarfrom WebLogic 12c common libraries.
weblogic.xml file in your application's
WEB-INF folder with the
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.
This error can occur on some Linux systems when using the embedded Derby database. Derby opens several file handles and may run over the maximum limit set by the system.
The solution is to increase the limit. The exact procedure varies from one Linux distribution to the next. The following works on Ubuntu. For other systems see the Too many open files wiki page for tips.
To set a system wide limit for open files on Ubuntu Linux:
sudo gedit /etc/security/limits.conf
* soft nofile 10000
* hard nofile 50000
sudo gedit /etc/pam.d/common-session
session required pam_limits.so
When installing or updating to a new version, you may see this error message:
This can be due to changes in signatures of classes that are stored in the user sessions (such as permissions, user, etc). The error happens when Tomcat attempts to de-serialize serialized sessions, that is when restarting the container.
This causes the loss of persisted sessions. Users will have to log in again. Otherwise it is a harmless error and can be ignored.
If you see the following error message in your logs:
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 the default port for Tomcat. You can see it at the end of the default address
. If another application on the computer is already using the same port you may need to change it.
<CATALINA_HOME>/conf/server.xmlin 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:
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.
/server/defaultBaseUrlproperty to http://localhost:8090/magnolia/
Now the Welcome page at
has the correct URLs too.
The port also needs to be changed in publishing configuration, otherwise activating changes from the author to public instance fails.
magnoliaPublic8080subscriber, set the
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.
Allow an exception in Windows Firewall for Java.
If you get a security alert during startup, check the Private networks checkbox and click Allow access.
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.
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.
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.
Increase Java heap size to allocate more memory to JVM:
/apache-tomcat/bin/setenv.baton Windows) in a text editor.
Xmxparameter to set a new maximum heap size. Default size for Magnolia is 512M, try a higher amount such as 1024M.
./magnolia_control.sh start && tail -f ../logs/catalina.out
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.