Even so, an app server utilizing more instances wont break the spec per
se...meaning, a spec built application will still run just fine. I can't
imagine that Sun dictates how a vendor must specifical handle
instances..that wouldn't break any application.
> -----Original Message-----
> From: richard wu [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 07, 2001 11:58 AM
> To: Orion-Interest
> Subject: Re: multiple instances of a servlet?
>
>
> The following is from spec 2.3:
>
> SRV.2.2 Number of Instances
> For a servlet not implementing SingleThreadModel and
> not hosted in a distributed
> environment (the default), the servlet container must
> use only one instance per serv-let
> declaration. A servlet declaration is part of the
> deployment descriptor of the web
> application containing the servlet, as described in
> Chapter SRV.13, "Deployment
> Descriptor"
>
>
> --- Ville Rinne <[EMAIL PROTECTED]> wrote:
> > We've implemented the request-controller pattern
> > using a servlet as the entry-point of all our
> > jsp-pages. For some reason Orion creates multiple
> > instances of this servlet even though it isn't
> > implementing SingleThreadModel and there isn't
> > anything peculiar about it. I have the servlet
> > printing to System.out every time init() is run and
> > every time it receives a request, it also prints the
> > memory address of the instance that's handling it.
> > For some reason with this servlet there are multiple
> > instances (up to 3 so far) that handle these
> > requests. There doesn't seem to be any larger logic
> > in which instance gets to handle the request. It's
> > not a problem per se but I just find it rather
> > strange since I assumed that only one instance of a
> > servlet would be created. Anyone else ran into this
> > ?
> >
> > cheers,
> > Ville Rinne
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with
> Yahoo! Messenger
> http://phonecard.yahoo.com/
>
