On Mon, Aug 31, 2015 at 6:11 PM, Stefan Eissing <[email protected]> wrote: > Hunting a bit on the "scoreboard is full, not at MaxRequestWorkers" issue, > I found that setting > > c->cs->state = CONN_STATE_LINGER;
mod_http2 could possiblly return CONN_STATE_WRITE_COMPLETION (with c->keepalive = AP_CONN_CLOSE, unless c->aborted), so that blocking writes (if any) can be scheduled (in event). > > explicitly on exiting connection processing (h2_conn.c) seems to help > with this. As an experiment, I set > > c->cs->state = CONN_STATE_READ_REQUEST_LINE; This state looks unhandled after ap_run_process_connecton, shouldn't happen :) The case should probably be handled like CONN_STATE_LINGER (or DEBUG_ASSERT?) since ptrans leaks... PR 53555 seems not related though, mpm_event and mod_http call ap_process_http_async_connection::ap_process_async_request::ap_process_request_after_handler() which do the right thing wrt cs->state. Regards, Yann.
