test case. There definitely is an issue here.
>> >> > At this point, the thread has already synchronized on the chain
>> >> > (due to the doIntercept method on the PhaseInterceptorChain being
>> >> > synchronized). Thus, some of the synchronized blocks
method on the PhaseInterceptorChain being
> >> > synchronized). Thus, some of the synchronized blocks in there
> >> > don't look correct. If I create a simple:
> >> >
> >> > final Object lock = new Object();
> >> >
> >> &g
t;> >
>> > in there, then that problem goes away.
>> >
>> > That said, I hit another couple of issues with your testcase as well
>> > that I'm looking into. :-(
>> >
>> > Dan
>> >
>> >> - Original Message ---
ow be fixed.
Dan
>
>
>
> - Original Message -
> From: "xuhb"
> To:
> Sent: Monday, August 22, 2011 11:06 AM
> Subject: Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor
>
>
>
> > Thanks Dan:
> >
> > I trie
as well
> > that I'm looking into. :-(
> >
> > Dan
> >
> >> - Original Message -
> >> From: "xuhb"
> >> To:
> >> Sent: Friday, August 19, 2011 1:39 PM
> >> Subject: Re: A mysteriously deadlock of CXF
-
>> From: "xuhb"
>> To:
>> Sent: Friday, August 19, 2011 1:39 PM
>> Subject: Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor
>>
>>
>>
>> > Sorry, I foget post the issue link:
>> >
>> > https://issues.apa
1:06 AM
Subject: Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor
> Thanks Dan:
>
> I tried, it's ok now;
> thanks to your rapid fix;
>
> - Original Message -
> From: "Daniel Kulp"
> To:
> Cc: "xuhb"
> Sent: Satur
Thanks Dan:
I tried, it's ok now;
thanks to your rapid fix;
- Original Message -
From: "Daniel Kulp"
To:
Cc: "xuhb"
Sent: Saturday, August 20, 2011 1:21 AM
Subject: Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor
>
> I just committed
ore chain.wait() return, the sync of chain will be
> re-locked, so it will block untill chain.resume() finished;
> - Original Message -
> From: "xuhb"
> To:
> Sent: Friday, August 19, 2011 1:39 PM
> Subject: Re: A mysteriously deadlock of CXF OnewayProcessorIntercep
said, I hit another couple of issues with your testcase as well that I'm
looking into. :-(
Dan
> - Original Message -
> From: "xuhb"
> To:
> Sent: Friday, August 19, 2011 1:39 PM
> Subject: Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor
>
urn, the sync of chain will be
> re-locked, so it will block untill chain.resume() finished;
>
> - Original Message -
> From: "xuhb"
> To:
> Sent: Friday, August 19, 2011 1:39 PM
> Subject: Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor
>
&g
Maybe it is becuase before chain.wait() return, the sync of chain will be
re-locked, so it will block untill chain.resume() finished;
- Original Message -
From: "xuhb"
To:
Sent: Friday, August 19, 2011 1:39 PM
Subject: Re: A mysteriously deadlock of CXF OnewayProcessorI
Sorry, I foget post the issue link:
https://issues.apache.org/jira/browse/CXF-3750
- Original Message -
From: "xuhb"
To:
Sent: Friday, August 19, 2011 1:34 PM
Subject: A mysteriously deadlock of CXF OnewayProcessorInterceptor
> Hi:
>Recently when I am chec
Hi:
Recently when I am checking/testing CXF , there is a mysteriously deadlock
of CXF Oneway Process; Normally CXF engine will invoke the one way bussiness
logical asynchronized ,, so the servlet handle will finished and return back to
servlet engine immediately;
But sometime, I notic
14 matches
Mail list logo
