[JS2-991] Issues with Tomcat 6

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.0
• Component/s: Application servers
• Environment: Jetspeed trunk 772355; Apache Tomcat 6.0.18
• Assignee: W. Randall Watler
• Reporter: Niels van Kampenhout
• Created: 06/May/09 19:39
• Updated: 04/Oct/11 21:08
• Resolved: 07/May/09 07:02

Description

Tomcat 6 configuration needs to be adjusted for Jetspeed to start and run properly (where Tomcat 5.5.26 works out of the box). In catalina.properties,

common.loader=${catalina.home}/lib,${catalina.home}/lib/*.jar

must be changed into

common.loader=${catalina.home}/lib,${catalina.home}/lib/.jar,${catalina.base}/lib/.jar,${catalina.base}/common/endorsed/.jar,${catalina.base}/shared/lib/.jar

Otherwise exceptions occur when starting Tomcat:

SEVERE: Error deploying configuration descriptor myportal.xml
java.lang.NoClassDefFoundError: org/apache/jetspeed/security/User

and

SEVERE: error stopping
LifecycleException: Pipeline has not been started

To reproduce

• download Tomcat 6.0.18 and unzip – do not touch any configuration files
• generate a custom portal with the maven archetype
• edit Jetspeed configuration and set server directory to location of downloaded/unzipped Tomcat 6.0.18
• build and deploy custom portal (mvn jetspeed:mvn -Dtarget=all)
• start Tomcat