You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Elliot Metsger (JIRA)" <ji...@apache.org> on 2007/06/02 08:22:15 UTC

[jira] Created: (PLUTO-376) Update Pluto installer to work with Tomcat 6.x

Update Pluto installer to work with Tomcat 6.x
----------------------------------------------

                 Key: PLUTO-376
                 URL: https://issues.apache.org/jira/browse/PLUTO-376
             Project: Pluto
          Issue Type: Improvement
          Components: maven pluto plugin
    Affects Versions: 1.1.3, 1.2.0
            Reporter: Elliot Metsger
            Assignee: Elliot Metsger
             Fix For: 1.2.0, 1.1.4


Update Pluto to work with Tomcat 6.x.

Most notably Tomcat 6.x does away with the classloader hierarchy <tomcat>/server, <tomcat>/common, <tomcat>/shared.  Everything by default is lumped into <tomcat>/lib.  The endorsed directory is now <tomcat>/endorsed.

Perhaps related is that Pluto crash and burns when starting up in Tomcat 6:
FINE:  [3] Creating portlet container...
Jun 2, 2007 2:10:42 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.apache.pluto.driver.PortalStartupListener
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
        at org.apache.pluto.PortletContainerFactory.<clinit>(PortletContainerFactory.java:36)
        at org.apache.pluto.driver.PortalStartupListener.initContainer(PortalStartupListener.java:180)
        at org.apache.pluto.driver.PortalStartupListener.contextInitialized(PortalStartupListener.java:126)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)


Moving webapps/pluto/WEB-INF/lib/commons-logging-api-1.1.jar to lib/ solves the problem.  I wonder if the thread that loads listener classes has <tomcat>/lib as its classloader versus <tomcat>/<webapp>/WEB-INF/lib

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

[jira] Updated: (PLUTO-376) Update Pluto installer to work with Tomcat 6.x

Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliot Metsger updated PLUTO-376:
---------------------------------

    Description: 
Update Pluto to work with Tomcat 6.x. 

Most notably Tomcat 6.x does away with the classloader hierarchy <tomcat>/server, <tomcat>/common, <tomcat>/shared. Everything by default is lumped into <tomcat>/lib. The endorsed directory is now <tomcat>/endorsed. 

Perhaps related is that Pluto crash and burns when starting up in Tomcat 6: 
FINE: [3] Creating portlet container... 
Jun 2, 2007 2:10:42 AM org.apache.catalina.core.StandardContext listenerStart 
SEVERE: Exception sending context initialized event to listener instance of class org.apache.pluto.driver.PortalStartupListener 
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory 
at org.apache.pluto.PortletContainerFactory.<clinit>(PortletContainerFactory.java:36) 
at org.apache.pluto.driver.PortalStartupListener.initContainer(PortalStartupListener.java:180) 
at org.apache.pluto.driver.PortalStartupListener.contextInitialized(PortalStartupListener.java:126) 
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) 
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) 


Moving webapps/pluto/WEB-INF/lib/commons-logging-api-1.1.jar to lib/ solves the problem. I wonder if the thread that loads listener classes has <tomcat>/lib as its classloader versus <tomcat>/<webapp>/WEB-INF/lib

  was:
Update Pluto to work with Tomcat 6.x.

Most notably Tomcat 6.x does away with the classloader hierarchy <tomcat>/server, <tomcat>/common, <tomcat>/shared.  Everything by default is lumped into <tomcat>/lib.  The endorsed directory is now <tomcat>/endorsed.

Perhaps related is that Pluto crash and burns when starting up in Tomcat 6:
FINE:  [3] Creating portlet container...
Jun 2, 2007 2:10:42 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.apache.pluto.driver.PortalStartupListener
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
        at org.apache.pluto.PortletContainerFactory.<clinit>(PortletContainerFactory.java:36)
        at org.apache.pluto.driver.PortalStartupListener.initContainer(PortalStartupListener.java:180)
        at org.apache.pluto.driver.PortalStartupListener.contextInitialized(PortalStartupListener.java:126)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)


Moving webapps/pluto/WEB-INF/lib/commons-logging-api-1.1.jar to lib/ solves the problem.  I wonder if the thread that loads listener classes has <tomcat>/lib as its classloader versus <tomcat>/<webapp>/WEB-INF/lib


In Tomcat 5.5, PortletContainerFactory had access to commons-logging-api from the "System" classloader.  Tomcat 5.5 included a copy of commons-logging-api in bin/commons-logging-api:
http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html#Class%20Loader%20Definitions

In Tomcat 6.x, there is no commons-logging-api in the "System" classloader:
http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html#Class%20Loader%20Definitions



> Update Pluto installer to work with Tomcat 6.x
> ----------------------------------------------
>
>                 Key: PLUTO-376
>                 URL: https://issues.apache.org/jira/browse/PLUTO-376
>             Project: Pluto
>          Issue Type: Improvement
>          Components: maven pluto plugin
>    Affects Versions: 1.2.0, 1.1.3
>            Reporter: Elliot Metsger
>            Assignee: Elliot Metsger
>             Fix For: 1.2.0, 1.1.4
>
>
> Update Pluto to work with Tomcat 6.x. 
> Most notably Tomcat 6.x does away with the classloader hierarchy <tomcat>/server, <tomcat>/common, <tomcat>/shared. Everything by default is lumped into <tomcat>/lib. The endorsed directory is now <tomcat>/endorsed. 
> Perhaps related is that Pluto crash and burns when starting up in Tomcat 6: 
> FINE: [3] Creating portlet container... 
> Jun 2, 2007 2:10:42 AM org.apache.catalina.core.StandardContext listenerStart 
> SEVERE: Exception sending context initialized event to listener instance of class org.apache.pluto.driver.PortalStartupListener 
> java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory 
> at org.apache.pluto.PortletContainerFactory.<clinit>(PortletContainerFactory.java:36) 
> at org.apache.pluto.driver.PortalStartupListener.initContainer(PortalStartupListener.java:180) 
> at org.apache.pluto.driver.PortalStartupListener.contextInitialized(PortalStartupListener.java:126) 
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) 
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) 
> Moving webapps/pluto/WEB-INF/lib/commons-logging-api-1.1.jar to lib/ solves the problem. I wonder if the thread that loads listener classes has <tomcat>/lib as its classloader versus <tomcat>/<webapp>/WEB-INF/lib

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

[jira] Updated: (PLUTO-376) Update Pluto to work with Tomcat 6.x

Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliot Metsger updated PLUTO-376:
---------------------------------

    Summary: Update Pluto to work with Tomcat 6.x  (was: Update Pluto installer to work with Tomcat 6.x)

> Update Pluto to work with Tomcat 6.x
> ------------------------------------
>
>                 Key: PLUTO-376
>                 URL: https://issues.apache.org/jira/browse/PLUTO-376
>             Project: Pluto
>          Issue Type: Improvement
>          Components: maven pluto plugin
>    Affects Versions: 1.2.0, 1.1.3
>            Reporter: Elliot Metsger
>            Assignee: Elliot Metsger
>             Fix For: 1.2.0, 1.1.4
>
>
> Update Pluto to work with Tomcat 6.x. 
> Most notably Tomcat 6.x does away with the classloader hierarchy <tomcat>/server, <tomcat>/common, <tomcat>/shared. Everything by default is lumped into <tomcat>/lib. The endorsed directory is now <tomcat>/endorsed. 
> Perhaps related is that Pluto crash and burns when starting up in Tomcat 6: 
> FINE: [3] Creating portlet container... 
> Jun 2, 2007 2:10:42 AM org.apache.catalina.core.StandardContext listenerStart 
> SEVERE: Exception sending context initialized event to listener instance of class org.apache.pluto.driver.PortalStartupListener 
> java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory 
> at org.apache.pluto.PortletContainerFactory.<clinit>(PortletContainerFactory.java:36) 
> at org.apache.pluto.driver.PortalStartupListener.initContainer(PortalStartupListener.java:180) 
> at org.apache.pluto.driver.PortalStartupListener.contextInitialized(PortalStartupListener.java:126) 
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) 
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) 
> Moving webapps/pluto/WEB-INF/lib/commons-logging-api-1.1.jar to lib/ solves the problem. I wonder if the thread that loads listener classes has <tomcat>/lib as its classloader versus <tomcat>/<webapp>/WEB-INF/lib

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

[jira] Resolved: (PLUTO-376) Update Pluto to work with Tomcat 6.x

Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliot Metsger resolved PLUTO-376.
----------------------------------

    Resolution: Fixed

> Update Pluto to work with Tomcat 6.x
> ------------------------------------
>
>                 Key: PLUTO-376
>                 URL: https://issues.apache.org/jira/browse/PLUTO-376
>             Project: Pluto
>          Issue Type: Improvement
>          Components: maven pluto plugin
>    Affects Versions: 1.2.0, 1.1.3
>            Reporter: Elliot Metsger
>            Assignee: Elliot Metsger
>             Fix For: 1.2.0, 1.1.4
>
>
> Update Pluto to work with Tomcat 6.x. 
> Most notably Tomcat 6.x does away with the classloader hierarchy <tomcat>/server, <tomcat>/common, <tomcat>/shared. Everything by default is lumped into <tomcat>/lib. The endorsed directory is now <tomcat>/endorsed. 
> Perhaps related is that Pluto crash and burns when starting up in Tomcat 6: 
> FINE: [3] Creating portlet container... 
> Jun 2, 2007 2:10:42 AM org.apache.catalina.core.StandardContext listenerStart 
> SEVERE: Exception sending context initialized event to listener instance of class org.apache.pluto.driver.PortalStartupListener 
> java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory 
> at org.apache.pluto.PortletContainerFactory.<clinit>(PortletContainerFactory.java:36) 
> at org.apache.pluto.driver.PortalStartupListener.initContainer(PortalStartupListener.java:180) 
> at org.apache.pluto.driver.PortalStartupListener.contextInitialized(PortalStartupListener.java:126) 
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) 
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) 
> Moving webapps/pluto/WEB-INF/lib/commons-logging-api-1.1.jar to lib/ solves the problem. I wonder if the thread that loads listener classes has <tomcat>/lib as its classloader versus <tomcat>/<webapp>/WEB-INF/lib

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

[jira] Closed: (PLUTO-376) Update Pluto to work with Tomcat 6.x

Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliot Metsger closed PLUTO-376.
--------------------------------


> Update Pluto to work with Tomcat 6.x
> ------------------------------------
>
>                 Key: PLUTO-376
>                 URL: https://issues.apache.org/jira/browse/PLUTO-376
>             Project: Pluto
>          Issue Type: Improvement
>          Components: maven pluto plugin
>    Affects Versions: 1.2.0, 1.1.3
>            Reporter: Elliot Metsger
>            Assignee: Elliot Metsger
>             Fix For: 1.2.0, 1.1.4
>
>
> Update Pluto to work with Tomcat 6.x. 
> Most notably Tomcat 6.x does away with the classloader hierarchy <tomcat>/server, <tomcat>/common, <tomcat>/shared. Everything by default is lumped into <tomcat>/lib. The endorsed directory is now <tomcat>/endorsed. 
> Perhaps related is that Pluto crash and burns when starting up in Tomcat 6: 
> FINE: [3] Creating portlet container... 
> Jun 2, 2007 2:10:42 AM org.apache.catalina.core.StandardContext listenerStart 
> SEVERE: Exception sending context initialized event to listener instance of class org.apache.pluto.driver.PortalStartupListener 
> java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory 
> at org.apache.pluto.PortletContainerFactory.<clinit>(PortletContainerFactory.java:36) 
> at org.apache.pluto.driver.PortalStartupListener.initContainer(PortalStartupListener.java:180) 
> at org.apache.pluto.driver.PortalStartupListener.contextInitialized(PortalStartupListener.java:126) 
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) 
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) 
> Moving webapps/pluto/WEB-INF/lib/commons-logging-api-1.1.jar to lib/ solves the problem. I wonder if the thread that loads listener classes has <tomcat>/lib as its classloader versus <tomcat>/<webapp>/WEB-INF/lib

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