Magnolia 6.1 reached end of life on March 31, 2021. This branch is no longer supported, see End-of-life policy.
...
Multiexcerpt include | ||||
---|---|---|---|---|
|
The NPE may be due to an incorrect initialization of I18nAuthoringSupport
. You may see an error like this in your logs:
If you are using JBoss 7.2 with JDK 11 to deploy Magnolia, you may get an error during installation. To resolve the issue, add the following lines to WEB-INF/jboss-deployment-structure.xml
:
Code Block |
---|
<deployment>
<dependencies>
<module name="jdk.unsupported"/>
</dependencies>
</deployment> |
If you are using the MySQL JDBC driver 8.0.x to install a new Magnolia instance, you may encounter the following error:
Code Block |
---|
2020-02-14 14:35:07,538 ERROR org.apache.jackrabbit.core.RepositoryImpl: |
Code Block |
2019-06-20 15:06:54,955 ERROR agnolia.ui.framework.app.AppInstanceControllerImpl: Sub-app [detail] of app [pages] failed to start java.lang.NullPointerExceptionRepository: null at info.magnolia.ui.framework.i18n.DefaultI18NAuthoringSupport.createI18NURI(DefaultI18NAuthoringSupport.java:154) |
Workaround: Restart your instances.
Your Magnolia instance starts up very slowly, noticeably more than before. You may encounter this after upgrading your macOS to Sierra 10.12 or later.
Workaround:
Open a terminal and figure out the hostname of your Mac. To get the hostname, use the command hostname
.
Code Block | ||
---|---|---|
| ||
hostname
joesLittleMacBookPro.local |
...
Add these two lines to /etc/hosts
:
Code Block | ||||
---|---|---|---|---|
| ||||
127.0.0.1 <hostname>
::1 <hostname> |
In place of <hostname>
, use your real hostname.
Most probably, your hosts file already contains entries starting with 127.0.0.1
and with ::1
. Just add the real hostname at the end of one line that starts with ::1
and at the end of another line that starts with 127.0.0.1
. Make sure to add a space character before the hostname.
With the given hostname, the two lines would look like this:
Code Block | ||||
---|---|---|---|---|
| ||||
127.0.0.1 localhost joesLittleMacBookPro.local
::1 localhost joesLittleMacBookPro.local |
...
Further information:
( Tested on Windows 10.) When starting up Tomcat with the Magnolia CLI mgnl start
command, you get a flickering window, the server hangs and nothing is written into the logs. To see the actual error, don't use Magnolia CLI to start Magnolia, start Tomcat directly with <your-magnolia-install-folder>\apache tomcat\bin\catalina.bat run
. This should start Magnolia in the same window and allow you to see the error message:
Code Block |
---|
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap |
The most likely cause is that you are trying to allocate too much heap space in the 32-bit JVM.
Solution: Replace the JVM with a 64-bit version.
See also: Why can't I get a larger heap with the 32-bit JVM?
You get the following error message after a fresh Java installation:
Code Block |
---|
Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
At least one of these environment variables is needed to run this program |
Solution: Set the variables through the "Edit the system environment variables" dialog.
If you get an error like this one:
Code Block |
---|
The JRE_HOME environment variable is not defined correctly
The environment variable is needed to run this program |
then you are most probably attempting to run Tomcat with the JAVA_HOME
variable set but without the JRE_HOME
variable defined.
Solution: Set the JRE_HOME
variable.
If you attempt to start Magnolia via 'mgnl start', and you see no startup executed, check if your JRE_HOME and your JAVA_HOME are set. If so, you may need to remove the environmental variable for JRE_HOME to get Magnolia to start properly.
Allow an exception in Windows Firewall for Java.
C:\Sun\SDK\jdk\bin\java.exe
.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.
Code Block |
---|
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.
When installing DX Core 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-dx-core-installer-x.y.z.jar
. Make sure the file extension is .jar. Internet Explorer has a tendency to append or change it to .zip.
...
Our default configuration uses the server mode for H2. If you migrate from Magnolia below 5.5.9 in the 5.5 branch or below 5.6.2 in the 5.6 branch and try to initiate a backup call using CLI or REST, it fails because H2 does not allow more than one connection at a time. Configure H2 to run in server mode by 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
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jackrabbit 2.16 introduced existence checks for node-types when refreshing indexing configurations. Previously it would accept arbitrary node-type names as strings. If your project is not using Magnolia's SearchIndex implementation, you may find the following messages in your logs:
Code Block | ||
---|---|---|
| ||
2018-07-25 17:48:33,691 WARN rabbit.core.query.lucene.IndexingConfigurationImpl: Unable to refresh index rules
javax.jcr.nodetype.NoSuchNodeTypeException: {http://www.magnolia.info/jcr/mgnl}page
at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.getNodeTypeDef(NodeTypeRegistry.java:552) ~[jackrabbit-core-2.16.1.jar:2.16.1] |
Code Block | ||
---|---|---|
| ||
2018-03-16 11:30:57,892 WARN rg.apache.jackrabbit.core.query.lucene.SearchIndex: Exception initializing indexing configuration from: /info/magnolia/jackrabbit/indexing_configuration_website.xml
javax.jcr.nodetype.NoSuchNodeTypeException: {http://www.magnolia.info/jcr/mgnl}page
at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.getNodeTypeDef(NodeTypeRegistry.java:552) ~[jackrabbit-core-2.16.1.jar:2.16.1] |
To mitigate this problem, replace in your Jackrabbit search configuration files
Code Block | ||
---|---|---|
| ||
<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex"> |
with
Code Block | ||
---|---|---|
| ||
<SearchIndex class="info.magnolia.jackrabbit.lucene.SearchIndex"> |
The warnings should not appear in the logs if you follow our recommendation to update first to the latest minor release version before upgrading to the most recent major release, see How to update.
The embedded Derby database, an option that can be used instead of the H2 database, 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.
...
title | Ubuntu Linux |
---|
ulimit -n
limits.conf
file: sudo gedit /etc/security/limits.conf
* soft nofile 10000
* hard nofile 50000
root
.sudo gedit /etc/pam.d/common-session
Add the following line to the file: session required pam_limits.so
Info |
---|
On *ubuntu 17.04 you'll probably also have to add the following line
to and to |
ulimit -n
Expand | ||
---|---|---|
| ||
OS X 10.8 Mountain Lion:
OS X 10.9 (Mavericks), 10.10 (Yosemite) and 10.11 (El Capitan), see Shell Session Limit OS X 10.12 (Sierra) and 10.13 (High Sierra), see the answer given for For OS X Sierra (10.12.X) on this page. |
When installing or updating to a new version, you may see this error message:
Code Block |
---|
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.
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.
...
Find the following section and set the value of port
to something other than 8080, for example 8090:
org.apache.jackrabbit.core.state.ItemStateException: failed to read bundle (stacktrace on DEBUG log level): deadbeef-face-babe-cafe-babecafebabe: java.sql.SQLSyntaxErrorException: Table '<DATABASE_NAME>.<TABLE_NAME>' doesn't exist |
This happens only when you install a new instance from scratch or create database tables during installation. As a workaround, use JDBC 5.1.x or create the tables manually in your database.
The NPE may be due to an incorrect initialization of I18nAuthoringSupport
. You may see an error like this in your logs:
Code Block |
---|
2019-06-20 15:06:54,955 ERROR agnolia.ui.framework.app.AppInstanceControllerImpl: Sub-app [detail] of app [pages] failed to start java.lang.NullPointerException: null at info.magnolia.ui.framework.i18n.DefaultI18NAuthoringSupport.createI18NURI(DefaultI18NAuthoringSupport.java:154) |
Workaround: Restart your instances.
Your Magnolia instance starts up very slowly, noticeably more than before. You may encounter this after upgrading your macOS to Sierra 10.12 or later.
Workaround:
Open a terminal and figure out the hostname of your Mac. To get the hostname, use the command hostname
.
Code Block | ||
---|---|---|
| ||
hostname
joesLittleMacBookPro.local |
The command returns the hostname of your Mac. In the given example, the hostname is joesLittleMacBookPro.local
.
/etc/hosts
with an editor of your choice. You will edit the file in the next step.root
. Your user must belong to the group admin; otherwise, you cannot save the changes to the file. You will be asked for your password either when opening the file or when trying to save it.Add these two lines to /etc/hosts
:
Code Block | ||||
---|---|---|---|---|
| ||||
127.0.0.1 <hostname>
::1 <hostname> |
In place of <hostname>
, use your real hostname.
Most probably, your hosts file already contains entries starting with 127.0.0.1
and with ::1
. Just add the real hostname at the end of one line that starts with ::1
and at the end of another line that starts with 127.0.0.1
. Make sure to add a space character before the hostname.
With the given hostname, the two lines would look like this:
Code Block | ||||
---|---|---|---|---|
| ||||
127.0.0.1 localhost joesLittleMacBookPro.local
::1 localhost joesLittleMacBookPro.local |
Further information:
( Tested on Windows 10.) When starting up Tomcat with the Magnolia CLI mgnl start
command, you get a flickering window, the server hangs and nothing is written into the logs. To see the actual error, don't use Magnolia CLI to start Magnolia, start Tomcat directly with <your-magnolia-install-folder>\apache tomcat\bin\catalina.bat run
. This should start Magnolia in the same window and allow you to see the error message:
Code Block |
---|
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap |
The most likely cause is that you are trying to allocate too much heap space in the 32-bit JVM.
Solution: Replace the JVM with a 64-bit version.
See also: Why can't I get a larger heap with the 32-bit JVM?
You get the following error message after a fresh Java installation:
Code Block |
---|
Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
At least one of these environment variables is needed to run this program |
Solution: Set the variables through the "Edit the system environment variables" dialog.
If you get an error like this one:
Code Block |
---|
The JRE_HOME environment variable is not defined correctly
The environment variable is needed to run this program |
then you are most probably attempting to run Tomcat with the JAVA_HOME
variable set but without the JRE_HOME
variable defined.
Solution: Set the JRE_HOME
variable.
If you attempt to start Magnolia via 'mgnl start', and you see no startup executed, check if your JRE_HOME and your JAVA_HOME are set. If so, you may need to remove the environmental variable for JRE_HOME to get Magnolia to start properly.
Allow an exception in Windows Firewall for Java.
C:\Sun\SDK\jdk\bin\java.exe
.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.
Code Block |
---|
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.
When installing DX Core 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-dx-core-installer-x.y.z.jar
. Make sure the file extension is .jar. Internet Explorer has a tendency to append or change it to .zip.
Include Page | ||||
---|---|---|---|---|
|
Our default configuration uses the server mode for H2. If you migrate from Magnolia below 5.5.9 in the 5.5 branch or below 5.6.2 in the 5.6 branch and try to initiate a backup call using CLI or REST, it fails because H2 does not allow more than one connection at a time. Configure H2 to run in server mode by 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
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jackrabbit 2.16 introduced existence checks for node-types when refreshing indexing configurations. Previously it would accept arbitrary node-type names as strings. If your project is not using Magnolia's SearchIndex implementation, you may find the following messages in your logs:
Code Block | ||
---|---|---|
| ||
2018-07-25 17:48:33,691 WARN rabbit.core.query.lucene.IndexingConfigurationImpl: Unable to refresh index rules
javax.jcr.nodetype.NoSuchNodeTypeException: {http://www.magnolia.info/jcr/mgnl}page
at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.getNodeTypeDef(NodeTypeRegistry.java:552) ~[jackrabbit-core-2.16.1.jar:2.16.1] |
Code Block | ||
---|---|---|
| ||
2018-03-16 11:30:57,892 WARN rg.apache.jackrabbit.core.query.lucene.SearchIndex: Exception initializing indexing configuration from: /info/magnolia/jackrabbit/indexing_configuration_website.xml
javax.jcr.nodetype.NoSuchNodeTypeException: {http://www.magnolia.info/jcr/mgnl}page
at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.getNodeTypeDef(NodeTypeRegistry.java:552) ~[jackrabbit-core-2.16.1.jar:2.16.1] |
To mitigate this problem, replace in your Jackrabbit search configuration files
Code Block | ||
---|---|---|
| ||
<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex"> |
with
Code Block | ||
---|---|---|
| ||
<SearchIndex class="info.magnolia.jackrabbit.lucene.SearchIndex"> |
The warnings should not appear in the logs if you follow our recommendation to update first to the latest minor release version before upgrading to the most recent major release, see How to update.
The embedded Derby database, an option that can be used instead of the H2 database, 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.
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
OS X 10.8 Mountain Lion:
OS X 10.9 (Mavericks), 10.10 (Yosemite) and 10.11 (El Capitan), see Shell Session Limit OS X 10.12 (Sierra) and 10.13 (High Sierra), see the answer given for For OS X Sierra (10.12.X) on this page. |
When installing or updating to a new version, you may see this error message:
Code Block |
---|
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.
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.
<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:
Code Block | ||||
---|---|---|---|---|
| ||||
<!-- 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 create absolute links in emails or other external systems. To do this, you need to now access Magnolia at the new port 8090.
http://localhost:8090/magnoliaAuthor/.magnolia
./server/defaultBaseUrl
property to http://localhost:8090/magnolia/
. http://localhost:8090/magnoliaPublic/.magnolia
./server/defaultBaseUrl
property to http://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.
magnoliaPublic8080
receiver (subscriber), set the URL
property to http://localhost:8090/magnoliaPublic
.magnoliaPublic8090
.Info |
---|
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 |
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.
Code Block | ||||
---|---|---|---|---|
| ||||
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:
./magnolia_control.sh stop
/apache-tomcat/bin/setenv.sh
(/apache-tomcat/bin/setenv.bat
on Windows) in a text editor.Xmx
parameter to set a new maximum heap size. Default size for Magnolia is 2048M, try a higher amount such as 4096M../magnolia_control.sh start && tail -f ../logs/catalina.out
For issues related to publishing/activation keys and the handshaking process, see either the Publishing errors page or the Activation errors page, depending on the module you use.
MAGNOLIA-6865 introduced a new security filter that checks each POST request. As this may affect the functionality of your existing forms, please contact us and we'll provide you with more information about this issue.
For security reasons, however, we cannot disclose further details on this page.
To mitigate an issue caused by having more than 500 configured virtual URI mappings in light modules, a WARN-level message is now logged when a DirectoryWatcher
overflow occurs (MAGNOLIA-7762). We recommend to keep the number of files in a single folder below 100 and to use folder hierarchies whenever possible. For the upcoming fix, see MAGNOLIA-7798.
If you search for content using searchfn.searchPage()
, searchfn.searchContent()
or by executing search queries directly from a template, the search result order will not respect the natural order. This issue is caused by a bug in Apache Jackrabbit filed as JCR-3932: "Result of JCR-SQL2 query doesn't respect document order in JCR".
Until the JCR bug is fixed, do not use searchfn
. To get the correct order, execute JCR XPath queries directly.
There are limitations related to the deep learning and search features of the Find Bar, which are provided by the Periscope and Periscope Result Ranker modules.
You should configure DL4J memory limits to avoid off-heap memory starvation. This is particularly the case with the -Dorg.bytedeco.javacpp.maxbytes
JVM argument. For more details, see MGNLPER-121.
When experiencing this issue, the following message can be found in the logs: java.lang.NoClassDefFoundError: Could not initialize class org.nd4j.linalg.factory
. The issue may appear even on more than just one Tomcat instance, running on the same VM and the same JDK.
The ndj4 library can only be initiated once. Therefore, result ranking on public instances should be disabled, which you can do either by changing the configuration of the Periscope Result Ranker module, or rather by completely removing the magnolia-periscope-result-ranker
module from your WAR package. After this modification, the search function will be available but search results will not be ranked. For more details see MGNLPER-112
...
<!-- 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.
http://localhost:8090/magnoliaAuthor/.magnolia
./server/defaultBaseUrl
property to http://localhost:8090/magnolia/
. http://localhost:8090/magnoliaPublic/.magnolia
./server/defaultBaseUrl
property to http://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.
magnoliaPublic8080
receiver (subscriber), set the URL
property to http://localhost:8090/magnoliaPublic
.magnoliaPublic8090
.Info |
---|
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 |
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:
./magnolia_control.sh stop
/apache-tomcat/bin/setenv.sh
(/apache-tomcat/bin/setenv.bat
on Windows) in a text editor.Xmx
parameter to set a new maximum heap size. Default size for Magnolia is 2048M, try a higher amount such as 4096M../magnolia_control.sh start && tail -f ../logs/catalina.out
For issues related to publishing/activation keys and the handshaking process, see either the Publishing errors page or the Activation errors page, depending on the module you use.
MAGNOLIA-6865 introduced a new security filter that checks each POST request. As this may affect the functionality of your existing forms, please contact us and we'll provide you with more information about this issue.
For security reasons, however, we cannot disclose further details on this page.