You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Sergey Beryozkin <sb...@progress.com> on 2009/09/03 12:41:03 UTC
Failing JMS Continuations test (Was : Re: Back to normal.....)
>> > There is a "randomly" failing continuations test that I've asked Sergey
>> > to look at, but it's failing on on the branches. If he cannot find a
>> > fix tomorrow, I'll @Ignore it for a bit.
Looking into it now... The initial observation is that it is always green if the test server (Server2) is started in the in-process
mode, all the 5 client threads get their expected responses back after firing at the same time but it fails as soon as the Server2
is launched in a seperate process... Not quite sure yet what does it indicate at...
cheers, Sergey
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
RE: Failing JMS Continuations test (Was : Re: Back to normal.....)
Posted by Sergey Beryozkin <sb...@progress.com>.
Thanks Dan for finding the actual issues with the ConduitSelector.
One thing this test has confirmed is that the way JMS continuations are
handled on the server side is pretty rock solid...
Cheers, Sergey
-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org]
Sent: 03 September 2009 18:54
To: dev@cxf.apache.org
Cc: Sergey Beryozkin; Benson Margulies
Subject: Re: Failing JMS Continuations test (Was : Re: Back to
normal.....)
OK. I'm pretty sure Sergey and I tracked this down to some thread
safety
issues in the ConduitSelector. However, it was made even worse on
2.2.x/2.1.x due to some additional thread safety issues in the
JMSConduit on
those branches. (trunk has a completely updated conduit that doesn't
suffer
the problem)
Anyway, I'm hoping the next round of hudson builds will be good. :-)
Dan
On Thu September 3 2009 6:41:03 am Sergey Beryozkin wrote:
> >> > There is a "randomly" failing continuations test that I've asked
> >> > Sergey to look at, but it's failing on on the branches. If he
cannot
> >> > find a fix tomorrow, I'll @Ignore it for a bit.
>
> Looking into it now... The initial observation is that it is always
green
> if the test server (Server2) is started in the in-process mode, all
the 5
> client threads get their expected responses back after firing at the
same
> time but it fails as soon as the Server2 is launched in a seperate
> process... Not quite sure yet what does it indicate at...
>
> cheers, Sergey
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Failing JMS Continuations test (Was : Re: Back to normal.....)
Posted by Daniel Kulp <dk...@apache.org>.
OK. I'm pretty sure Sergey and I tracked this down to some thread safety
issues in the ConduitSelector. However, it was made even worse on
2.2.x/2.1.x due to some additional thread safety issues in the JMSConduit on
those branches. (trunk has a completely updated conduit that doesn't suffer
the problem)
Anyway, I'm hoping the next round of hudson builds will be good. :-)
Dan
On Thu September 3 2009 6:41:03 am Sergey Beryozkin wrote:
> >> > There is a "randomly" failing continuations test that I've asked
> >> > Sergey to look at, but it's failing on on the branches. If he cannot
> >> > find a fix tomorrow, I'll @Ignore it for a bit.
>
> Looking into it now... The initial observation is that it is always green
> if the test server (Server2) is started in the in-process mode, all the 5
> client threads get their expected responses back after firing at the same
> time but it fails as soon as the Server2 is launched in a seperate
> process... Not quite sure yet what does it indicate at...
>
> cheers, Sergey
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog