well this issue is maybe something else (we fixed a concurrent error for 1.7.2 IIRC, can be linked), but logback ch.qos.logback.core.util.Loader#getResource ignores classloader hierarchy so you can't have 2 concurrent configs in a tree
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-05-15 10:34 GMT+02:00 hwaastad <he...@waastad.org>: > Hi, I've been playing around some more and it's definitly a classloading > issue. > > This is my observations: > 1. skipped logback on tomee global > > 2. added an logback-config jar which I <unpack> in the ear (also added > <includeInApplicationXml>true</includeInApplicationXml> in jarModule to get > it working) > > 3. I kind of pushing initialization a little bit here since having two > schedulers running in two different projects (at the same time) an this > generates a: > SEVERE - The bean instance WebScheduler threw a system > exception:java.lang.LinkageError: loader (instance of > org/apache/openejb/util/classloader/URLClassLoaderFirst): attempted > duplicate class definition for name: "org/slf4j/LoggerFactory" > > If one of them is startup, initialization is OK. > > br hw > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Ear-Logback-revisit-tp4674809p4674830.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
