Re: multiple instances of a servlet?
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, Rafaelmailto:[EMAIL PROTECTED]
Re: multiple instances of a servlet?
Daniel, So far I've just been running it on a test-platform using just the default web-application. I haven't defined any additional names for it. However, Richard Wu's mail where he pasted this from the spec: "For a servlet not implementing SingleThreadModel and not hosted in a distributed environment (the default), " got me thinking that as we have our servers configured to run in a cluster would that affect this ? And indeed this is a bit of a problem, like in our case the request-controller reads and caches the page-information from the db, now if I want to refresh the cache without restarting the server I can't control which instance of the servlet will get refreshed .. - Original Message - From: "Daniel López" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Wednesday, August 08, 2001 10:04 AM Subject: Re: multiple instances of a servlet? > Hi Ville, > > Do you, by any chance, have different names defined for your controller > servlet in the web.xml file? I also have my own ControllerServlet > framework and I just have a single instance, unless I define more than > one name for the same servlet. If you define different web applications > you would also have different instances, even if you use the same name, > so have a look at your web.xml files to see if the problem is in there. > Just my 2ec, > D. > > > Ville Rinne wrote: > > > > Kevin, let me know how your tests came out. I did some more testing myself > > and I found it strange that when I created a specific simple test-servlet > > for this case I didn't manage to get more than one instance of it created. > > I'll do some more testing tomorrow but there is definitely something > > strange going on. Obviously the amount my testservlet takes to complete a > > request is smaller than the amount of time my request-controller takes but > > at this point I honestly don't have a clue :P > > > > Anyhow, since servlets aren't synchronized in any way by default, how > > would it increase performance even if there was more than one instance of > > them in existance? > > > > cheers, > > Ville Rinne > > > > Of course it isn't a huge problem > > > > On Tue, 7 Aug 2001, Duffey, Kevin wrote: > > > > > Keep in mind that every app server is allowed to implement the spec in their > > > own manner. It does sound peculiar, but it is very possible that Orion gets > > > its performance by pooling a few servlet instances even without the single > > > threaded model. I don't know for sure, but that seems logical. By having > > > even two or three instances, it could increase the ability to handle ore > > > requests..although myself I thought that a single instance would be plenty > > > fast to have literally thousands of requests per second hit it. Each time a > > > request comes in, the container should create a new thread for that request > > > then send it on its way to the servlet instance. A PIII600 system can run > > > over 1billion instructions per second. Figure that with the JVM interpreter, > > > your code and any resources, you should still be able to iterate thousands > > > of requests per second, unless object creation in a servlet (and depending > > > on what it is doing) slows things down. The one factor I am not sure of is > > > how many "threads" a JVM can handle at one time. I have heard of single > > > servers handling 1000's of hits per second, and if each request goes to a > > > JSP or servlet, that should equate to one new thread per request..even if > > > the session id is the same (for example, the user somehow opened a new > > > window from the browser window..and could possibly submit two (or more) > > > requests at the same time). > > > > > > At any rate, it sounds to me like perhaps either there is a bug, or that > > > Orion is doing this pooling automatically to increase performance. > > > Interesting though..I will now check out to see if my MVC framework does the > > > same thing. > > > > > > > > > > > > -Original Message- > > > From: Ville Rinne [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, August 07, 2001 7:59 AM > > > To: Orion-Interest > > > Subject: multiple instances of a servlet? > > > > > > > > > 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
Re: multiple instances of a servlet?
Maybe you should read my entire message since I clearly stated that I wasn't using SingleThreadModel .. - Original Message - From: "Richard Wu" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Wednesday, August 08, 2001 3:45 AM Subject: Re: multiple instances of a servlet? > if you really care performance, you shouldn't use singlethreadmodel in first > place. > - Original Message - > From: "Ville Rinne" <[EMAIL PROTECTED]> > To: "Orion-Interest" <[EMAIL PROTECTED]> > Sent: Tuesday, August 07, 2001 7:06 PM > Subject: RE: multiple instances of a servlet? > > > > Kevin, let me know how your tests came out. I did some more testing myself > > and I found it strange that when I created a specific simple test-servlet > > for this case I didn't manage to get more than one instance of it created. > > I'll do some more testing tomorrow but there is definitely something > > strange going on. Obviously the amount my testservlet takes to complete a > > request is smaller than the amount of time my request-controller takes but > > at this point I honestly don't have a clue :P > > > > Anyhow, since servlets aren't synchronized in any way by default, how > > would it increase performance even if there was more than one instance of > > them in existance? > > > > cheers, > > Ville Rinne > > > > Of course it isn't a huge problem > > > > On Tue, 7 Aug 2001, Duffey, Kevin wrote: > > > > > Keep in mind that every app server is allowed to implement the spec in > their > > > own manner. It does sound peculiar, but it is very possible that Orion > gets > > > its performance by pooling a few servlet instances even without the > single > > > threaded model. I don't know for sure, but that seems logical. By having > > > even two or three instances, it could increase the ability to handle ore > > > requests..although myself I thought that a single instance would be > plenty > > > fast to have literally thousands of requests per second hit it. Each > time a > > > request comes in, the container should create a new thread for that > request > > > then send it on its way to the servlet instance. A PIII600 system can > run > > > over 1billion instructions per second. Figure that with the JVM > interpreter, > > > your code and any resources, you should still be able to iterate > thousands > > > of requests per second, unless object creation in a servlet (and > depending > > > on what it is doing) slows things down. The one factor I am not sure of > is > > > how many "threads" a JVM can handle at one time. I have heard of single > > > servers handling 1000's of hits per second, and if each request goes to > a > > > JSP or servlet, that should equate to one new thread per request..even > if > > > the session id is the same (for example, the user somehow opened a new > > > window from the browser window..and could possibly submit two (or more) > > > requests at the same time). > > > > > > At any rate, it sounds to me like perhaps either there is a bug, or that > > > Orion is doing this pooling automatically to increase performance. > > > Interesting though..I will now check out to see if my MVC framework does > the > > > same thing. > > > > > > > > > > > > -Original Message- > > > From: Ville Rinne [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, August 07, 2001 7:59 AM > > > To: Orion-Interest > > > Subject: multiple instances of a servlet? > > > > > > > > > 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 > > > > > > > > > >
Re: multiple instances of a servlet?
Hi Ville, Do you, by any chance, have different names defined for your controller servlet in the web.xml file? I also have my own ControllerServlet framework and I just have a single instance, unless I define more than one name for the same servlet. If you define different web applications you would also have different instances, even if you use the same name, so have a look at your web.xml files to see if the problem is in there. Just my 2ec, D. Ville Rinne wrote: > > Kevin, let me know how your tests came out. I did some more testing myself > and I found it strange that when I created a specific simple test-servlet > for this case I didn't manage to get more than one instance of it created. > I'll do some more testing tomorrow but there is definitely something > strange going on. Obviously the amount my testservlet takes to complete a > request is smaller than the amount of time my request-controller takes but > at this point I honestly don't have a clue :P > > Anyhow, since servlets aren't synchronized in any way by default, how > would it increase performance even if there was more than one instance of > them in existance? > > cheers, > Ville Rinne > > Of course it isn't a huge problem > > On Tue, 7 Aug 2001, Duffey, Kevin wrote: > > > Keep in mind that every app server is allowed to implement the spec in their > > own manner. It does sound peculiar, but it is very possible that Orion gets > > its performance by pooling a few servlet instances even without the single > > threaded model. I don't know for sure, but that seems logical. By having > > even two or three instances, it could increase the ability to handle ore > > requests..although myself I thought that a single instance would be plenty > > fast to have literally thousands of requests per second hit it. Each time a > > request comes in, the container should create a new thread for that request > > then send it on its way to the servlet instance. A PIII600 system can run > > over 1billion instructions per second. Figure that with the JVM interpreter, > > your code and any resources, you should still be able to iterate thousands > > of requests per second, unless object creation in a servlet (and depending > > on what it is doing) slows things down. The one factor I am not sure of is > > how many "threads" a JVM can handle at one time. I have heard of single > > servers handling 1000's of hits per second, and if each request goes to a > > JSP or servlet, that should equate to one new thread per request..even if > > the session id is the same (for example, the user somehow opened a new > > window from the browser window..and could possibly submit two (or more) > > requests at the same time). > > > > At any rate, it sounds to me like perhaps either there is a bug, or that > > Orion is doing this pooling automatically to increase performance. > > Interesting though..I will now check out to see if my MVC framework does the > > same thing. > > > > > > > > -Original Message- > > From: Ville Rinne [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, August 07, 2001 7:59 AM > > To: Orion-Interest > > Subject: multiple instances of a servlet? > > > > > > 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
RE: multiple instances of a servlet?
You are correct..I didn't even consider instance variables such as used for a request counter to any given servlet. Good point. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Joel Shellman > Sent: Tuesday, August 07, 2001 2:43 PM > To: Orion-Interest > Subject: RE: multiple instances of a servlet? > > > Not true. Since the spec says only one instance, the programmer could > assume this and utilize instance variables. This would not work as > expected (per spec) if there were multiple instances handling requests. > It is arguably a bad idea, but there are situations where it might be > useful and would work "according to spec" but multiple instances would > break it. > > -- > Joel Shellman > Full Service Internet Solutions -- Contact us today for a free > consultation! > [Design | Flash | eCommerce | Backend | Database | Marketing] > iKestrel, Inc. http://www.ikestrel.com/ > > On 07 Aug 2001 12:28:17 -0700, Duffey, Kevin wrote: > > 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. > > >
Re: multiple instances of a servlet?
if you really care performance, you shouldn't use singlethreadmodel in first place. - Original Message - From: "Ville Rinne" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Tuesday, August 07, 2001 7:06 PM Subject: RE: multiple instances of a servlet? > Kevin, let me know how your tests came out. I did some more testing myself > and I found it strange that when I created a specific simple test-servlet > for this case I didn't manage to get more than one instance of it created. > I'll do some more testing tomorrow but there is definitely something > strange going on. Obviously the amount my testservlet takes to complete a > request is smaller than the amount of time my request-controller takes but > at this point I honestly don't have a clue :P > > Anyhow, since servlets aren't synchronized in any way by default, how > would it increase performance even if there was more than one instance of > them in existance? > > cheers, > Ville Rinne > > Of course it isn't a huge problem > > On Tue, 7 Aug 2001, Duffey, Kevin wrote: > > > Keep in mind that every app server is allowed to implement the spec in their > > own manner. It does sound peculiar, but it is very possible that Orion gets > > its performance by pooling a few servlet instances even without the single > > threaded model. I don't know for sure, but that seems logical. By having > > even two or three instances, it could increase the ability to handle ore > > requests..although myself I thought that a single instance would be plenty > > fast to have literally thousands of requests per second hit it. Each time a > > request comes in, the container should create a new thread for that request > > then send it on its way to the servlet instance. A PIII600 system can run > > over 1billion instructions per second. Figure that with the JVM interpreter, > > your code and any resources, you should still be able to iterate thousands > > of requests per second, unless object creation in a servlet (and depending > > on what it is doing) slows things down. The one factor I am not sure of is > > how many "threads" a JVM can handle at one time. I have heard of single > > servers handling 1000's of hits per second, and if each request goes to a > > JSP or servlet, that should equate to one new thread per request..even if > > the session id is the same (for example, the user somehow opened a new > > window from the browser window..and could possibly submit two (or more) > > requests at the same time). > > > > At any rate, it sounds to me like perhaps either there is a bug, or that > > Orion is doing this pooling automatically to increase performance. > > Interesting though..I will now check out to see if my MVC framework does the > > same thing. > > > > > > > > -Original Message- > > From: Ville Rinne [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, August 07, 2001 7:59 AM > > To: Orion-Interest > > Subject: multiple instances of a servlet? > > > > > > 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 > > > > >
RE: multiple instances of a servlet?
Kevin, let me know how your tests came out. I did some more testing myself and I found it strange that when I created a specific simple test-servlet for this case I didn't manage to get more than one instance of it created. I'll do some more testing tomorrow but there is definitely something strange going on. Obviously the amount my testservlet takes to complete a request is smaller than the amount of time my request-controller takes but at this point I honestly don't have a clue :P Anyhow, since servlets aren't synchronized in any way by default, how would it increase performance even if there was more than one instance of them in existance? cheers, Ville Rinne Of course it isn't a huge problem On Tue, 7 Aug 2001, Duffey, Kevin wrote: > Keep in mind that every app server is allowed to implement the spec in their > own manner. It does sound peculiar, but it is very possible that Orion gets > its performance by pooling a few servlet instances even without the single > threaded model. I don't know for sure, but that seems logical. By having > even two or three instances, it could increase the ability to handle ore > requests..although myself I thought that a single instance would be plenty > fast to have literally thousands of requests per second hit it. Each time a > request comes in, the container should create a new thread for that request > then send it on its way to the servlet instance. A PIII600 system can run > over 1billion instructions per second. Figure that with the JVM interpreter, > your code and any resources, you should still be able to iterate thousands > of requests per second, unless object creation in a servlet (and depending > on what it is doing) slows things down. The one factor I am not sure of is > how many "threads" a JVM can handle at one time. I have heard of single > servers handling 1000's of hits per second, and if each request goes to a > JSP or servlet, that should equate to one new thread per request..even if > the session id is the same (for example, the user somehow opened a new > window from the browser window..and could possibly submit two (or more) > requests at the same time). > > At any rate, it sounds to me like perhaps either there is a bug, or that > Orion is doing this pooling automatically to increase performance. > Interesting though..I will now check out to see if my MVC framework does the > same thing. > > > > -Original Message- > From: Ville Rinne [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, August 07, 2001 7:59 AM > To: Orion-Interest > Subject: multiple instances of a servlet? > > > 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 > >
RE: multiple instances of a servlet?
Not true. Since the spec says only one instance, the programmer could assume this and utilize instance variables. This would not work as expected (per spec) if there were multiple instances handling requests. It is arguably a bad idea, but there are situations where it might be useful and would work "according to spec" but multiple instances would break it. -- Joel Shellman Full Service Internet Solutions -- Contact us today for a free consultation! [Design | Flash | eCommerce | Backend | Database | Marketing] iKestrel, Inc. http://www.ikestrel.com/ On 07 Aug 2001 12:28:17 -0700, Duffey, Kevin wrote: > 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.
RE: multiple instances of a servlet?
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/ >
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/
RE: multiple instances of a servlet?
Keep in mind that every app server is allowed to implement the spec in their own manner. It does sound peculiar, but it is very possible that Orion gets its performance by pooling a few servlet instances even without the single threaded model. I don't know for sure, but that seems logical. By having even two or three instances, it could increase the ability to handle ore requests..although myself I thought that a single instance would be plenty fast to have literally thousands of requests per second hit it. Each time a request comes in, the container should create a new thread for that request then send it on its way to the servlet instance. A PIII600 system can run over 1billion instructions per second. Figure that with the JVM interpreter, your code and any resources, you should still be able to iterate thousands of requests per second, unless object creation in a servlet (and depending on what it is doing) slows things down. The one factor I am not sure of is how many "threads" a JVM can handle at one time. I have heard of single servers handling 1000's of hits per second, and if each request goes to a JSP or servlet, that should equate to one new thread per request..even if the session id is the same (for example, the user somehow opened a new window from the browser window..and could possibly submit two (or more) requests at the same time). At any rate, it sounds to me like perhaps either there is a bug, or that Orion is doing this pooling automatically to increase performance. Interesting though..I will now check out to see if my MVC framework does the same thing. -Original Message-From: Ville Rinne [mailto:[EMAIL PROTECTED]]Sent: Tuesday, August 07, 2001 7:59 AMTo: Orion-InterestSubject: multiple instances of a servlet? 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
Re: multiple instances of a servlet?
Isn't the way SingleThreadModel supposed to work? --- 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/
multiple instances of a servlet?
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
