it would use Servlet instance pooling.
- Original Message -
From: Shapira, Yoav [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, June 14, 2004 8:22 PM
Subject: RE: Multiple requests sharing the same Servlet instance
Hi,
I don't think your understanding is correct
.
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Keith Hankin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 9:14 AM
To: Tomcat Users List
Subject: Re: Multiple requests sharing the same Servlet instance
So this means that only one instance of a given
]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 6:47 PM
Subject: RE: Multiple requests sharing the same Servlet instance
Hi,
No, it doesn't mean one instance of a servlet class is created. It
means the container is free to pool the instances any which way it
likes
-
From: Keith Hankin [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 8:33 AM
Subject: Re: Multiple requests sharing the same Servlet instance
But if a Servlet instance might be used by multiple threads at one time,
then what's the point of having
Hi,
But if a Servlet instance might be used by multiple threads at one
time,
then what's the point of having Servlet object pooling at all? Why
wouldn't
It might and it might not. My point was that the Servlet Spec leaves it
for the container implementation to decide, and so you should be
PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 7:06 PM
Subject: RE: Multiple requests sharing the same Servlet instance
Hi,
But if a Servlet instance might be used by multiple threads at one
time,
then what's the point of having Servlet object pooling at all
no local
state is useful.
- Original Message -
From: Shapira, Yoav [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 7:06 PM
Subject: RE: Multiple requests sharing the same Servlet instance
Hi,
But if a Servlet instance might be used by multiple threads
On Wed, Jun 16, 2004 at 07:53:07PM +0530, Keith Hankin wrote:
: Maybe I'm being dumb, but it seems to me that based upon what I'm hearing,
: there is no benefit of doing Servlet instance pooling since the Servlets
: aren't true objects; they are merely places to put code, since no local
: state is
]
Sent: Wednesday, June 16, 2004 7:06 PM
Subject: RE: Multiple requests sharing the same Servlet instance
Hi,
But if a Servlet instance might be used by multiple threads at one
time,
then what's the point of having Servlet object pooling at all? Why
wouldn't
It might
Yes, those are useful objects, but they can be set at init() time, so there
is no point in pooling since only one instance is needed.
- Original Message -
From: QM [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 8:04 PM
Subject: Re: Multiple
this type of different state is useful since the developer does not have any
control over when Servlets are instantiated.
- Original Message -
From: QM [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 8:04 PM
Subject: Re: Multiple requests sharing the same
Hi,
I don't think your understanding is correct: the container may allow
multiple threads to use the same servlet instance concurrently. If you
need synchronization around or within that method, or around some fields
in your servlet class, you are responsible for it.
The container does
Wrong. It is expected that many threads may be executing the service() method
of a servlet at the same time.
One way to get around this is by making your serlvet implement
SingleThreadModel. (ick!)
-Tim
Keith Hankin wrote:
I am having a problem where one Servlet instance seems to being used by
MatrixOne Tech Support eMail incident submission functionality requires specific
subject line. The following subject lines are recognized.
Request for CustomerLink Access
- This will submit a request for new CustomerLink account
Request for CustomerLink Password Reset
- This will
On Mon, Jun 14, 2004 at 10:55:44AM -0400, Tim Funk wrote:
: One way to get around this is by making your serlvet implement
: SingleThreadModel. (ick!)
Not if the OP is using Tomcat5, or any other servlet spec 2.4 container.
;)
SingleThreadModel has (thankfully) been banished.
-QM
--
-feira, 29 de outubro de 2003 9:55
Para: Tomcat Users List
Assunto: Re: Multiple requests to the same servlet is problem
Can you post the servlet code?
Are you using global variables in you logic?
If so, you probably have a threading issue.
On Wednesday 29 October 2003 08:07 am
Sounds like your servlet is not thread-safe. Have you got any instance
variables declared in your servlet class?
-Original Message-
From: Edson Alves Pereira [mailto:[EMAIL PROTECTED]
Sent: 29 October 2003 13:07
To: 'Tomcat-User List'
Subject: Multiple requests to the same servlet is
Enviada: quarta-feira, 29 de outubro de 2003 9:08
Para: 'Tomcat Users List'
Assunto: RE: Multiple requests to the same servlet is problem
Sounds like your servlet is not thread-safe. Have you got any instance
variables declared in your servlet class?
-Original
PROTECTED]
Sent: 29 October 2003 13:49
To: 'Tomcat Users List'
Subject: RE: Multiple requests to the same servlet is problem
There´s no variable that would control that behavior, if reload each
iframe, one after another, it fine ( using mouse for example ). But tell me,
a thread-safe servlet
Can you post the servlet code?
Are you using global variables in you logic?
If so, you probably have a threading issue.
On Wednesday 29 October 2003 08:07 am, you wrote:
Hello folks, i have one page with iframes, each iframe has a GET
request, to a servlet that must bring description
-
From: Alex Fernández [mailto:[EMAIL PROTECTED]]
Sent: 23 May 2001 16:34
To: [EMAIL PROTECTED]
Subject: Re: Multiple requests
So, just to clarify:
The request arrives, Tomcat processes it and sends it to your servlet.
You do:
response.setContentType(text/html);
// commits
Hi David!
You can commit the response, and then the request will not be
resubmitted. But it's difficult, since the problem was that Tomcat is
not honoring the requests, to begin with.
In iPlanet, you can tell how many requests can be queued; it would be
interesting to know whether you can do
and
that a response will be along shortly. Is this what the SC_CONTINUE header
does, or is there another header I can send.
Thanks.
Dave
[EMAIL PROTECTED]
-Original Message-
From: Alex Fernández [mailto:[EMAIL PROTECTED]]
Sent: 23 May 2001 14:50
To: [EMAIL PROTECTED]
Subject: Re: Multiple
Message-
From: Alex Fernández [mailto:[EMAIL PROTECTED]]
Sent: 23 May 2001 14:50
To: [EMAIL PROTECTED]
Subject: Re: Multiple requests
Hi David!
You can commit the response, and then the request will not be
resubmitted. But it's difficult, since the problem was that Tomcat
:34
To: [EMAIL PROTECTED]
Subject: Re: Multiple requests
So, just to clarify:
The request arrives, Tomcat processes it and sends it to your servlet.
You do:
response.setContentType(text/html);
// commits the response
response.flushBuffer();
and, while your servlet thinks
25 matches
Mail list logo
