Committed some fixes for this to the 2.7.x branch. Would be great if you could
try the snapshots. Since it’s not easily reproduced, I’m not really sure it’s
fixed. If you see it again, definitely get new stack traces to me.
Dan
On Nov 8, 2013, at 4:46 AM, Jason Pell wrote:
> We use the
We use the maven wait plugin to wait for the ?wsdl url to return a 200 code
for the web services we need to use in soapui for integration builds.
We are now investigating other ways of working around this.
But i am relieved you replied as i am a little lost and reproducing the
thread dead lock is
The irony of this was that I first looked at this yesterday while sitting in a
session at WJAX entitled “Concurrency: The Good, The Bad, The Ugly”. :-(
The GOOD news is this won’t occur with 3.0/trunk. The QueryHandlers are gone
and thus the one lookup wouldn’t happen.
It seems like your s
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" wrote:
> Hi,
>
> I am continuing to try and understand the thread dump myself, but here it
>
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 wrote:
> Hi,
>
> I am getting intermittent dead lock on startup of my application. Th
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(ExtensionManag
