People with in insight into your connection state handling, please review: https://bz.apache.org/bugzilla/show_bug.cgi?id=63534
describes an issue with HTTP/2 and KeepAliveTimeout. Basically, HTTP/2 writes response DATA, gets blocked on HTTP/2 flow control, and makes a blocking READ on the connection. Since the only thing that can move things forward is a packet from the client. This triggers the KeepAlive behaviour of our connections, which is not what should apply here. The alternatives I can see are: 1. non-blocking reads and therefore continue to block a worker 2. twiddle the server->keepalive setting, question is, will that influence the mpm? Thanks for your help in this, Stefan
