Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of tnppresentation@gmail.com
 designates 74.125.82.43 as permitted sender)
MIME-Version: 1.0
Date: Tue, 10 Jan 2012 23:25:35 +1100
Message-ID: 
 <CAKTigKCM3JQ466R9iXP9zwB=ernaE0-9oyZb3FM57HnOf7yc9w@mail.gmail.com>
Subject: multi-tented connection queues
From: Tharindu Patikirikorala <tnppresentation@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=f46d04182552b46b1a04b62b9c06

--f46d04182552b46b1a04b62b9c06
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi All,


I am doing a case study to make tomcat to host multi-tented web
applications. i.e., a single web application/service container is serving
logically partitioned customers.  For the basic implementation (let=92s say
number of customers/tenant are 2) I want to make following modifications.

1)      Identify the tenant and implementing a request/connection queues
for each tenant. Then queue will have =91acceptcount=92 which reject the sy=
stem
to avoid severe overloads.

2)      The worker threads have to be allocated to serve these requests
based on a new scheduling. Two queues will be processed by this scheduler
based on a priority scheme.

After looking at the code, currently a single connection queue
(ServerSocket.listen(backlog)) is used which is not aware about the tenants
request. However, for the implementation we need another level of queuing
which will reject the requests based on the tenant.

Please suggest a way to implement such a scheme.


Thank you

Pati

--f46d04182552b46b1a04b62b9c06--