Hi wonder if it is not fixed on snapshots (if you can try it would be welcomed since we'll release 1.7.2 soon)
as a workaround you can prevload the locking classes in a ServletContextListener. Should not be the sexiest but the easiest to setup. 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-03-27 15:59 GMT+01:00 tschuler <[email protected]>: > Hi! > > We use TomEE 1.7.1 and get in troubles from time to time because of a > thread > dead lock resulting in an idle TomEE. It is always the same pattern as > shown > below - deadlock at > org.apache.openejb.util.classloader.URLClassLoaderFirst. > > Extract from JVisualVM thread dump: > > Found one Java-level deadlock > ============================= > EjbTimerPool - 2 > waiting to lock monitor 0x00000000221a3f88 (object 0x00000006c1886f50, a > org.apache.openejb.util.classloader.URLClassLoaderFirst), > which is held by JmsResourceAdapter-worker- - 6 > JmsResourceAdapter-worker- - 6 > waiting for ownable synchronizer 0x00000006c13b0cc0, (a > java.util.concurrent.locks.ReentrantLock$NonfairSync), > which is held by JmsResourceAdapter-worker- - 7 > JmsResourceAdapter-worker- - 7 > waiting to lock monitor 0x00000000221a3f88 (object 0x00000006c1886f50, a > org.apache.openejb.util.classloader.URLClassLoaderFirst), > which is held by JmsResourceAdapter-worker- - 6 > > Is there a way to get rid off the potential thread deadlock? > > Best regards, > Thomas > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/thread-deadlock-at-URLClassLoaderFirst-tp4674197.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
