I got further by copying log4j.jar in CATALINA_BASE/lib folder, but then I got next NoClassDefFoundError. Most confusing is that the same application deployed in TomEE Version 1.5.0 works perfectly. I believe it is some kind of class loader issue. Are there some significant class loader changes between version 1.5.0 and 1.5.1? It looks like that container is loading some classes from container provided commons-logging.jar first, and then can't find some classes in WEB-APP/lib which needed by commons-logging.
-----Ursprüngliche Nachricht----- Von: Romain Manni-Bucau [mailto:[email protected]] Gesendet: Montag, 4. Februar 2013 12:13 An: [email protected] Betreff: Re: AW: Class loading problem in TomEE 1.5.1 Hard to help since we dont "see" the issue You probably have some conflict in your app. Check your deps maybe Le 4 févr. 2013 12:11, <[email protected]> a écrit : > I have tried both: with commons-logging in my war file and without. > With same result(exception) in both cases. > I have tried to isolate the issue in small sample app, but without > success. Unfortunately I can't provide full application for reproduction. > Could you give some hints, how can I help you to reproduce the problem > on your side or solve the issue by myself? > > > > Note: did you put commons-logging in your app too? > > > can you reproduce it in a sample webapp? >
