History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: MAGNOLIA-1958
Type: Bug Bug
Status: Closed Closed
Resolution: Workaround exists
Priority: Blocker Blocker
Assignee: Vivian Steller
Reporter: Vivian Steller
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Magnolia

Cannot run Magnolia due to ERROR "Unable to initialize repository: Provider org.apache.xalan.processor.TransformerFactoryImpl not found"

Created: 13/Dec/07 04:53 PM   Updated: 14/Dec/07 06:30 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Environment:
- Platform Fedora 8 Linux (kernel 2.6.23.8-63.fc8) running in VMware workstation 6
- Tomcat 5.0.28, JDK version 1.5.0_13-b05.
Issue Links:
duplicate
 

Resolution Date: 14/Dec/07 06:30 PM
Date of First Response: 14/Dec/07 01:00 AM


 Description  « Hide
This report was forwarded from Magnolia Support:

Experience as follows.

-Tomcat starts no problem, sample apps work.

-Install magnolia-bundled-webapp-3.5.jar

-Error in catalina.out reads:

ERROR info.magnolia.jackrabbit.ProviderImpl ProviderImpl.java(init:213) 13.12.2007 09:26:16 Unable to initialize repository: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found

-Shutdown tomcat, copy xalan-2.4.0.jar to webapps/magnolia-bundled-webapp-3.5/WEB-INF/lib, restart Tomcat

-Now error in catalina.out reads :

---------------------------------------------
MAGNOLIA LICENSE
---------------------------------------------
Version number : 3.5
Build : 12. December 2007
Edition : Community Edition
Provider : Magnolia International (info@magnolia.info)
INFO info.magnolia.cms.beans.config.ConfigLoader ConfigLoader.java(load:133) 13.12.2007 09:29:27 Initializing content repositories
Dec 13, 2007 9:29:27 AM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Dec 13, 2007 9:29:27 AM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors
INFO info.magnolia.cms.beans.config.ShutdownManager ShutdownManager.java(execute:128) 13.12.2007 09:29:27 Executing shutdown tasks
Shutting down Log4J
WARN: The method class org.apache.commons.logging.impl.SLF4JLogFactory#release() was invoked.
WARN: Please see http://www.slf4j.org/codes.html for an explanation.

-Add export "JAVA_OPTS=-Xms256M -Xmx256M" to Tomcat's startup.sh script. Restart Tomcat.

-Error remains :

---------------------------------------------
MAGNOLIA LICENSE
---------------------------------------------
Version number : 3.5
Build : 12. December 2007
Edition : Community Edition
Provider : Magnolia International (info@magnolia.info)
INFO info.magnolia.cms.beans.config.ConfigLoader ConfigLoader.java(load:133) 13.12.2007 09:31:07 Initializing content repositories
Dec 13, 2007 9:31:07 AM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Dec 13, 2007 9:31:07 AM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors
INFO info.magnolia.cms.beans.config.ShutdownManager ShutdownManager.java(execute:128) 13.12.2007 09:31:07 Executing shutdown tasks
Shutting down Log4J
WARN: The method class org.apache.commons.logging.impl.SLF4JLogFactory#release() was invoked.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Vivian Steller - 13/Dec/07 05:32 PM
Cannot reproduce this issue on MacOS 10.4 with tomcat 5.0.28, JDK version 1.5.0_07-87.

However, we experienced similar issues, see MAGNOLIA-1782 for a solution. Basically once you put in xalan.jar you shouldn't forget to delete the repositories folder since it might hold corrupt .xml files.



Philipp Bracher - 14/Dec/07 11:35 AM
In case you run into that issue you have to do the following:
  • put the xalan jar to WEB-INF/lib
  • delete the created repositories directory (corrupt fails were created during the first startup)

We will put the the installation page


Gregory Joseph - 14/Dec/07 01:10 PM
changing fix version to 3.5.2 and leaving open as a reminder for documentation notes, but will then close with no fix version as it's likely there's nothing else we can do.

Gregory Joseph - 14/Dec/07 06:30 PM
Not much we can do about this AFAIK.
Please see comments for workarounds.
Will be mentionned in docs / release notes shortly.