So the spring launcher and jaxws endpoint are both trying to access the spring beans map at same time. I have not found a solution so far.
Sent from my Android phone On 07/11/2013 9:32 AM, "Jason Pell" <[email protected]> wrote: > Hi, > > I am continuing to try and understand the thread dump myself, but here it > is in case anyone feels like giving me some pointers :-) > > http://pastebin.com/p75BtvPk > > > On Thu, Nov 7, 2013 at 9:22 AM, Jason Pell <[email protected]> wrote: > >> Hi, >> >> I am getting intermittent dead lock on startup of my application. The >> two threads that are locking are accessing: >> >> java.lang.Thread.State: BLOCKED (on object monitor) >> INFO | jvm 1 | 2013/11/07 08:50:30 | at >> org.apache.cxf.bus.extension.ExtensionManagerImpl.getExtension(ExtensionManagerImpl.java:257) >> INFO | jvm 1 | 2013/11/07 08:50:30 | - waiting to lock >> <0x00000007ee31c6b0> (a org.apache.cxf.bus.extension.ExtensionManagerImpl) >> >> And... >> >> java.lang.Thread.State: BLOCKED (on object monitor) >> INFO | jvm 1 | 2013/11/07 08:50:29 | at >> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:181) >> >> >> We did not notice this with spring 3.1.2 >> >> We also don't get this all the time. None of our developers get it on >> their Linux Mint based machines, but we do on Centos 6.3. >> >> But the JVMs are exactly the same - both 64bit and actually the same tar >> ball. >> >> >> >
