On Mon, Dec 29, 2014 at 7:16 PM, Yuri <yuri@xxxxxxxxx> wrote: > I have a question about the situation that happens with Apache with > Wikimedia app. > In short, Apache begins to break connections when there are many concurrent > requests. > (Here is the bug report that I created for wikipedia > https://phabricator.wikimedia.org/T85191). > Connections are broken after http request is complete, but 'Connection: > keep-alive' has been set by the server in the last response. > The event MPM does this as a specific process runs out of threads, in the hope that there are other processes in better shape. If it didn't, and the keepalive connections became ready, they would queue. > I view this a violation of RFC2616 because server breaks connection without > letting the client know. A client, server, or proxy MAY close the transport connection at any time. For example, a client might have started to send a new request at the same time that the server has decided to close the "idle" connection. From the server's point of view, the connection is being closed while it was idle, but from the client's point of view, a request is in progress. This means that clients, servers, and proxies MUST be able to recover from asynchronous close events. > My questions are: > What could be misconfigured in Apache? Or maybe this is considered normal > that it breaks connections? Seems normal, albeit relatively new in event in 2.4? > Is there an option that Apache slows down clients without disconnecting in > case of congestion? http://httpd.apache.org/docs/2.4/mod/event.html#asyncrequestworkerfactor --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|