I'm still working on the fix, which is (sigh) taking longer than I'd have hoped.
The fix will actually go into the trunk first then very shortly after that into M2 - I was already working in the same area in the trunk so it was easier to do it that way round. Andrew On Wed, 2007-05-16 at 13:54 +0100, Rupert Smith wrote: > Yes, I'd heard from Rob that Gordon might have fixed this? Maybe a checkin > for the fix is still pending? I wanted to run my performance test suite > against the C++ broker yesterday, on M2 branch, but found that if I didn't > limit the message rate severely it would jam up. Would be nice to know the > status. > > Rupert > > On 16/05/07, Kevin Smith <[EMAIL PROTECTED]> wrote: > > > > I've heard that the C++ broker has concurrency issues -- can anyone > > confirm > > this? I'm running into a situation where more than two concurrent clients > > cause > > the broker to wedge itself at 100% CPU and never return. > > > > --Kevin > >
