> >>> "Christopher K. St. John" <[EMAIL PROTECTED]> 03-Nov-00 5:14:19 PM
> >>>
>
> >The same sort of problem can happen if, say, you're using
> >a threadpool and one servlet's doGet() blocks for a long
> >time. Eventually that will run your threadpool down and
> >you're stuck. Since java can't do anything about it, it's
> >like you're back in the the (shudder) days of cooperative
> >multitasking: the servlet has to follow the rules or else.
>
> Yes that's true but it's the same with any threadin system.
>
> Doing threading well requires a certain amount of co-operation and
> good behaviour.
In my understanding of this, the thread pools used in the well designed
servlet containers ( I have seen paperclips source) are dynamic in size and
if such a blocking is observed, new threads will be created on the fly. The
pool may in such a situation stabilize at a larger no of threads than
initialized with. Of course there is a tremendous overhead associated with
creating new threads but that is only till the pool stabalizes at a new
value.
What can be the disadvantage of situation above?
>
> Nic
>
Regds,
Gokul
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
