<OK. Reposting>
Here is a clue:
--------------
Servlet 2.2 Specs:
For a servlet not implementing SingleThreadModel and not hosted in a distributed
environment (the default), the servlet container must use only one instance
per servlet 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”
------------
m2c
>If you declare the same servlet twice in the web.xml (i.e, different
>name, same class) you get two instances running. Check out your
>web.xml and let us know.
>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 ?
--
Best regards,
Rafael mailto:[EMAIL PROTECTED]
