tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergio Juan" <>
Subject Re: Forking high loaded servlet
Date Fri, 04 Jul 2003 13:25:46 GMT

----- Original Message ----- 
From: "Diego Castillo" <>
To: <>
Sent: Friday, July 04, 2003 3:05 PM
Subject: Forking high loaded servlet

> Hi all,
> I have a servlet that receives a heavy load. I would like to process
> multiple requests in parallel in order to increase throughput.
> Tomcat creates one single instance of the servlet. This is right
> according to servlet specification paragraph 3.2, but it does not suit
> my needs.
> I have tried extending SingleThreadModel and Tomcat does create multiple
> instances, but I get the exact same throughput.

Tomcat automatically creates one thread per request. If your servlet does
not have synchronization issues, it will be the same creating an object per
thread that using the same object (in fact a little heavier in the first
case, because of the overhead of creating objects).
> I have also tried launching a new thread for handling HttpServletRequest
> & HttpServletResponse, but as soon as the servlet exits service(), the
> response output stream gets closed by Tomcat.
Same here.. you are launching a Thread inside of an already independent

> Is there any spec compliant strategy to increase the number of requests
> per second that a servlet can handle?
In configuration you can set the processors number, but I think it is not
the issue. If the problem is that you got a bottleneck in your host (CPU or
disk at nearly 100%) you should consider load balancing between multiple
servers in different machines or using common programming performance tricks
(but I think you have already done that).


> Thanks in advance,
> Diego
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message