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 dk...@apache.org http://www.dankulp.com/blog
