The servlet is blocked with one thread inside it. When you make the call
with another browser window it starts NEW SECOND thread. This thread is NOT
LET INTO the servlet because it implements the SingleThreadModel and there
is ALREADY ONE THREAD INSIDE IT.
The 4.1 on W2K seems to be incorrect - it should behave like 3.2.1 on
linux!!!!
> -----Original Message-----
> From: Patricio Vera S. [SMTP:[EMAIL PROTECTED]]
> Sent: 10 December 2002 03:22
> To: [EMAIL PROTECTED]
> Subject: Re: servlet implementing SingleThreadModel
>
> That's is the idea, block the servlet so when call with another
> browser
> instance force to execute a new thread....
>
> It's semms ok in tomcat 4.1 on W2K but not in tomcat 3.2.1 on linux.
>
> Saludos,
> Patricio Vera S.
>
>
> ----- Original Message -----
> From: "Partha Ranjan Das" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, December 10, 2002 3:10 AM
> Subject: Re: servlet implementing SingleThreadModel
>
>
> > if (sOpcion.equals("SS")) {
> > > > while ( true )
> > > > ;
> > > > }
> > What does this code do? it will loop eternally.
> >
> > -----Original Message-----
> > From: Adrian Janssen [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, December 10, 2002 12:27 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: servlet implementing SingleThreadModel
> >
> >
> > SingleThreadModel means that only one thread is allowed to run in your
> > servlet at a time. So what is happening is with your first call to the
> > servlet a thread starts to execute in the servlet - but it never leaves
> the
> > servlet, as per yopur code. It thereby blocks the second call which will
> > start a new thread that will try to run through the servlet but due to
> the
> > fact the thread from the first call is still running in the servlet the
> > second call's thread is blocked due to the restrictions of the
> > SingleThreadModel.
> >
> > So if anything the W2K implementation seems like it might be incorrect,
> but
> > I suspect that it is setup differently, perhaps with a very short
> timeout.
> >
> > Cheers
> > Adrian
> >
>
--
It is the strict policy of Truworths that its e-mail facility and all
e-mail communications emanating therefrom, should be utilised for
business purposes only and should conform to high professional and
business standards. Truworths has stipulated certain regulations in
terms whereof strict guidelines relating to the use and content of
e-mail communications are laid down. The use of the Truworths e-mail
facility is not permitted for the distribution of chain letters or
offensive mail of any nature whatsoever. Truworths hereby distances
itself from and accepts no liability in respect of the unauthorised
use of its e-mail facility or the sending of e-mail communications
for other than strictly business purposes. Truworths furthermore
disclaims liability for any unauthorised instruction for which
permission was not granted. Truworths Limited accepts no liability
for any consequences arising from or as a result of reliance on this
message unless it is in respect of bona fide Truworths business for
which proper authorisation has been granted.
Any recipient of an unacceptable communication, a chain letter or
offensive material of any nature is requested to notify the Truworths
e-mail administrator ([EMAIL PROTECTED]) immediately in order that
appropriate action can be taken against the individual concerned.
___________________________________________________________________________
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
