On Sun, Sep 30, 2018 at 08:22:23PM +0200, Willy Tarreau wrote: > On Sun, Sep 30, 2018 at 07:59:34PM +0200, PiBa-NL wrote: > > Indeed it works with 1.8, so in that regard i 'think' the test itself is > > correct.. Also when disabling threads, or running only 1 client, it still > > works.. Then both CumConns CumReq show 11 for the first stats result. > > Hmmm for me it fails even without threads. That was the first thing I > tried when meeting the error in fact. But I need to dig deeper.
So I'm seeing that in fact the count is correct if the server connection closes first, and wrong otherwise. In fact it fails similarly both for 1.6, 1.7, 1.8 and 1.9 with and without threads. I'm seeing that the connection count is exactly 10 times the incoming connections while the request count is exactly 20 times this count. I suspect that what happens is that the request count is increased on each connection when preparing to receive a new request. This even slightly reminds me something but I don't know where I noticed something like this, I think I saw this when reviewing the changes needed to be made to HTTP for the native internal representation. So I think it's a minor bug, but not a regression. Thanks, Willy
