On 12/09/2010 17:45, Mark Thomas wrote:
> Digging into the root causes of [1] it appears that there are a number
> of threading / timing issues with the current AsyncContextImpl. Running
> the provided test case with ab -n 50 -c 20 triggers the error every
> couple of runs. The error appears to occ
Digging into the root causes of [1] it appears that there are a number
of threading / timing issues with the current AsyncContextImpl. Running
the provided test case with ab -n 50 -c 20 triggers the error every
couple of runs. The error appears to occur when the thread where
complete() is called fi
