[ 
https://issues.apache.org/jira/browse/TOMEE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Louis MONTEIRO updated TOMEE-217:
--------------------------------------

        Fix Version/s: 1.5.0
    Affects Version/s:     (was: 1.5.0)
                       1.0.0
    
> log4j integration issue
> -----------------------
>
>                 Key: TOMEE-217
>                 URL: https://issues.apache.org/jira/browse/TOMEE-217
>             Project: TomEE
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Mark Struberg
>             Fix For: 1.5.0
>
>
> we use log4j in our own jar
> ./webapps/course/WEB-INF/lib/log4j-1.2.16.jar
> TomEE packages slf4j which is most probably the reason for the following 
> exception:
> 06.06.2012 10:54:33 org.apache.tomee.catalina.TomcatWebAppBuilder 
> startInternal
> SCHWERWIEGEND: Unable to deploy collapsed ear in war /course: Exception: 
> Creating application failed: /opt/apache/tomee/webapps/course: 
> java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: 
> org/apache/log4j/Priority: java.lang.NoClassDefFoundError: 
> org/apache/log4j/Priority
> org.apache.openejb.OpenEJBException: Creating application failed: 
> /opt/apache/tomee/webapps/course: java.util.concurrent.ExecutionException: 
> java.lang.NoClassDefFoundError: org/apache/log4j/Priority: 
> java.lang.NoClassDefFoundError: org/apache/log4j/Priority
>       at 
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:911)
>       at 
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:508)
>       at 
> org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:671)
>       at 
> org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:624)
>       at 
> org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:117)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to