--
Sorry, I can't tell you about using a thread pool (or only the few
things following in the next section), but I think creating a new thread
for each request is one of the best features of servlets.
It makes sure that your servlet can respond in every situation, and it's
much less memory and cpu usage than with C, C++ or perl which spawn a
new process for every request (plus all the init overhead).
Maybe one solution for using a thread pool is to use a main servlet that
implements SingleThreadModel and than call the servlet that should
respond to that request. You can than start this servlet in one of the
thread of the thread pool. Of course, the so used servlet also has to
implement SingleThreadModel (I guess that's the name of that thing,
never used it).
Bibhas Bhattacharya wrote:
>
> --
>
> Platform: JServ1.0 NT4.0 Sp4 IBM JDK 1.1.7
>
> My earlier question may not have been very clear.
>
> JServ appears to be spawning a new thread for every request. This is
> obviously not the best way to do things. In the documentation there is hint
> on thread pooling support. Does anyone know how to pre-create and use a
> pool of threads with JServ?
>
> Thanks,
>
> Bibhas.
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> READ THE FAQ!!!! <http://java.apache.org/faq/>
> Archives and Other: <http://java.apache.org/main/mail.html/>
> Problems?: [EMAIL PROTECTED]
--
Guenther Wieser
creative-it/Guenther Wieser Software KEG
Student of Telematik at Graz University of Technology
http://www.creative-it.com mailto:[EMAIL PROTECTED]
-> In A World Without Walls And Fences, Who Needs Windows And Gates? <-
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
