* Bivens, Raymond E. <[EMAIL PROTECTED]> [020221 16:29]:
> List-
>
> We're implementing a web-based conformance testing client which could tie up
> a servlet for a couple of minutes while it tests a server somewhere else on
> the web. Since the tests can be quite lengthy anyway, my logic is to use a
> single threaded model--each client will grab a new servlet instance from the
> pool and wait while the servlet performs various tests on a remote server.
> Once the tests are complete, the servlet will reply back to the waiting
> client with the test results and return to the pool.
>
> How does Tomcat implement the single thread model for servlets? Will I be
> able to configure the number of servlet instances I need in the pool, or
> does Tomcat use multiples of the same instance? Any other thoughts would be
> appreciated...
By default, each registered name of a servlet has a separate instance.
Every request becomes a new thread running on that instance.
I *think* that by implementing a single threaded model, you're effectively
declaring run to be synchronised, which means that any clients trying to
use the servlet will block until the last client exits.
Which is A Bad Thing.
--
Serocki's Stricture:
Marriage is always a bachelor's last option.
Rasputin :: Jack of All Trades - Master of Nuns ::
___________________________________________________________________________
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
