tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mladen Turk <mt...@apache.org>
Subject Re: Hybrid (NIO+Multithread, SSL enabled) architecture for Coyote
Date Wed, 25 May 2005 16:50:03 GMT
Remy Maucherat wrote:
>>
>> In my mind, the argument for tomcat supporting 1000 concurrent
>> connections for an extended period of time isn't valid from my
>> experience.
> 
> - all the other APR features which are really useful and not provided by 
> the core Java platform



Actually I just read a perfect use case scenario request for
the new APR connector on tomcat-user@.
With only couple of threads all the 1000 connections could be handled
without having 1000 threads.


 > Users are connecting to the solution by invoking a servlet (runned by 
tomcat).
 > If a user is auhentified, then I use HTTPServletResponse object (in 
the service
 > method) to get the Outputstream of that object => 
HTTPServletResponse.getoutputstream)
 >
 > Then this stream will be use to handle communications between my 
client application
 > and my custom Server Process (I need to send real time informations 
through
 > this canal).
 >
 > Important => A client session can last several hours, so the life of the
 > servlet is set to time infinite .
 >
 > In fact I had the idea delegate socket connection managment, to 
tomcat engine,
 > by setting servlet life time to infinite.
 >
 > Is it a good way to do, or should I use a socket pooling algorithm 
(actualy,
 > the server can freeze, after unregular amout of times, time for 
writing operation
 > in the Output stream can increase until being totaly unusuable, I have to
 > close, and reconnect)
 >
 > The objective is to handle more than 1000 client sessions.



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


Mime
View raw message