Return-Path: 
 <users-return-254423-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
X-Original-To: apmail-tomcat-users-archive@www.apache.org
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D2A1618A88
	for <apmail-tomcat-users-archive@www.apache.org>;
 Tue, 18 Aug 2015 03:40:25 +0000 (UTC)
Received: (qmail 9024 invoked by uid 500); 18 Aug 2015 03:40:22 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 8968 invoked by uid 500); 18 Aug 2015 03:40:22 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 8956 invoked by uid 99); 18 Aug 2015 03:40:22 -0000
Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Aug 2015 03:40:22 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org)
 with ESMTP id 0E54719D212
	for <users@tomcat.apache.org>; Tue, 18 Aug 2015 03:40:22 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 3.962
X-Spam-Level: ***
X-Spam-Status: No, score=3.962 tagged_above=-999 required=6.31
	tests=[DATE_IN_PAST_06_12=1.103, FSL_HELO_BARE_IP_2=1.999,
	HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_NUMERIC_HELO=0.865,
	RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, URIBL_BLOCKED=0.001]
	autolearn=disabled
Received: from mx1-eu-west.apache.org ([10.40.0.8])
	by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new,
 port 10024)
	with ESMTP id 9-WdgxdWyaS4 for <users@tomcat.apache.org>;
	Tue, 18 Aug 2015 03:40:12 +0000 (UTC)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
	by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with
 ESMTPS id 31D1720D31
	for <users@tomcat.apache.org>; Tue, 18 Aug 2015 03:40:11 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
	(envelope-from <jak-tomcat-user@m.gmane.org>)
	id 1ZRXkp-0003bD-Jn
	for users@tomcat.apache.org; Tue, 18 Aug 2015 05:40:04 +0200
Received: from 130.14.254.24 ([130.14.254.24])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <users@tomcat.apache.org>; Tue, 18 Aug 2015 05:40:03 +0200
Received: from dan by 130.14.254.24 with local (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <users@tomcat.apache.org>; Tue, 18 Aug 2015 05:40:03 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: users@tomcat.apache.org
From: Daniel Davis <dan@danizen.net>
Subject: Re: Any way to deal with too many request per second?
Date: Mon, 17 Aug 2015 21:25:44 +0000 (UTC)
Lines: 14
Message-ID: <loom.20150817T231814-742@post.gmane.org>
References: 
 <CA+WmwVR17beSTf_fMhWD3VERE4eBJRaGsTEi01vv=+vrwXhu8w@mail.gmail.com>
 <4FF4E163.7050509@christopherschultz.net>
 <049F90AE-A789-4329-A3E5-0062C14E563C@charmides.in-berlin.de>
 <4FF6DC8F.8090207@christopherschultz.net>
 <CABOBwRjz=-hLEG94XNDXrgjfLTr+XxO5tUm+iGFDnHzsiJaf7g@mail.gmail.com>
 <4FF72377.4090508@christopherschultz.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: sea.gmane.org
User-Agent: Loom/3.14 (http://gmane.org/)
X-Loom-IP: 130.14.254.24 (Mozilla/5.0 (Windows NT 6.1;
 WOW64) AppleWebKit/537.36 (KHTML,
 like Gecko) Chrome/44.0.2403.155 Safari/537.36)

2012/7/6 Christopher Schultz <chris <at> christopherschultz.net>:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> 
>> It is unreasonable to queue requests as a mitigation for high
>> load: you will only make things worse for your clients.

Tomcat already does this - https://tomcat.apache.org/tomcat-6.0-
doc/config/executor.html

Jetty includes a QoS filter which might be adapted - 
http://www.eclipse.org/jetty/documentation/9.2.6.v20141205/qos-
filter.html



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org