portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-991) Issues with Tomcat 6
Date Wed, 06 May 2009 21:55:30 GMT

    [ https://issues.apache.org/jira/browse/JS2-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706614#action_12706614

Ate Douma commented on JS2-991:

Sounds cool!

However, I think we no longer need nor should support Tomcat5.
Tomcat itself doesn't even list that version any more on their homepage.
Furthermore, Tomcat5.0.x required a different context file structure, so supporting that needs
us maintaining (at least) two different context file definitions as well.

I actually want to state we can/should only (formally) support Tomcat 5.5.27+ or Tomcat 6.0.18+.

Tomcat 5.5.23 worked fine, but thereafter they broke JAAS support with 5.5.24 and 5.5.25.
When 5.5.26 came out, it turned out they "flipped" the logic for the Realm useContextClassLoader
attribute setting (now needs to be "true" while on 5.5.23 it needed to be "false").
But 5.5.26 had several other big problems which got eventually fixed with release 5.5.27.
Version 5.5.27 luckily works fine again.

Similar problems existed with early Tomcat6, but since version 6.0.18 it actually works very
nicely, and the same context file as needed for 5.5.26+ can be used for 6.0.18+ as well.

> Issues with Tomcat 6
> --------------------
>                 Key: JS2-991
>                 URL: https://issues.apache.org/jira/browse/JS2-991
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Application servers
>    Affects Versions: 2.2.0
>         Environment: Jetspeed trunk 772355
> Apache Tomcat 6.0.18
>            Reporter: Niels van Kampenhout
>            Assignee: Randy Watler
>             Fix For: 2.2.0
> 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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message