Gordon Sim wrote:
Kevin Smith 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.
Yes, I'm afraid that is the case. It uses a single apr pool for all apr
allocated objects which means that any concurrent destruction of such
objects can lead to an infinite loop in the apr pool cleanup code.
A fix is hopefully coming shortly.
Thanks for the update! If there are any patches for this against M2, I'd be
willing to help test.
--Kevin
