geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Han Hong Fang (JIRA)" <>
Subject [jira] [Commented] (GERONIMO-5671) Webapplication fails to start: java.lang.ClassNotFoundException: org.apache.log4j.CategoryKey
Date Thu, 07 Jul 2011 08:38:16 GMT


Han Hong Fang commented on GERONIMO-5671:

nexus-webapp-1.8.0.war now can be deployed with updated deployment plan (attached as nexus-webapp-1.8.0(updated).plan),
but still failed with the same root cause as reported. The root cause is that ServletContext.getRealPath()
returns null in geronimo 3.0 which leads to cannot be loaded. We can JIRA
opened for this issue:

As to the elements supported in deployment plan, you are right that <inverse-classloading>
isn't supported in Geronimo 3.0. <hidden-classes> is also removed with a replacement

<hidden-classes>javax.faces</hidden-classes> would be <import-package>!javax.faces</import-package>

> Webapplication fails to start: java.lang.ClassNotFoundException: org.apache.log4j.CategoryKey
> ---------------------------------------------------------------------------------------------
>                 Key: GERONIMO-5671
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 3.0
>         Environment: Ubuntu 10.10
> Java 1.6.0_22
> x86
>            Reporter: Christian Domsch
>            Assignee: Han Hong Fang
>         Attachments: geronimo.log, geronimo2.log, nexus-webapp-1.8.0(updated).plan, nexus-webapp-1.8.0.plan
> When I try to deploy the nexus webapp from sonatype (version 1.8.0), the deployed application
cannot be started. The underlying exception is the ClassNotFoundException from the summary.
In 2.x version I used to circumvent classloading issues by using the <hidden-classes>
and <inverse-classloading> tags in the deployment plan, but this doesn't seem to work
> Attached are my deployment-plan and the compete stacktrace from the geronimo-console.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message