> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: [totally OT] Tomcat Behavior on Multiple HTTP requests from same
> browser
> > > Or swallows and coconuts.
> > Someone had to bring that up. African or European?
> > I think we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 3/22/13 12:35 PM, André Warnier wrote:
> Caldarale, Charles R wrote:
>>> From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
>>> Subject: RE: [a bit, but not totally OT] Tomcat Behavior on
>>> Mu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
On 3/22/13 10:25 AM, Caldarale, Charles R wrote:
>> From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
>> Subject: RE: [a bit, but not totally OT] Tomcat Behavior on
>> Multiple HTTP requests from same browser
>
On 3/22/2013 9:35 AM, André Warnier wrote:
Caldarale, Charles R wrote:
From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] Subject:
RE: [a bit, but not totally OT] Tomcat Behavior on Multiple HTTP
requests from same browser
You would need a fairly large, and well-disciplined team of
Caldarale, Charles R wrote:
From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
Subject: RE: [a bit, but not totally OT] Tomcat Behavior on Multiple HTTP requests from same browser
You would need a fairly large, and well-disciplined team of pigeons to
do that though. I don't think
> From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
> Subject: RE: [a bit, but not totally OT] Tomcat Behavior on Multiple HTTP
> requests from same browser
> > You would need a fairly large, and well-disciplined team of pigeons to
> > do that though. I don't
but not totally OT] Tomcat Behavior on Multiple
> > HTTP requests from same browser
> >
> > Christopher Schultz wrote:
> > > HTTP connections for long periods of time, but that's really abuse of
> > > the protocol IMO. You can send bowling balls via carri
> -Original Message-
> From: André Warnier [mailto:a...@ice-sa.com]
> Sent: Thursday, March 21, 2013 8:51 AM
> To: Tomcat Users List
> Subject: Re: [a bit, but not totally OT] Tomcat Behavior on Multiple
> HTTP requests from same browser
>
> Christopher Schultz wro
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 3/21/13 7:15 AM, André Warnier wrote:
Christopher Schultz wrote:
I think there might be a problem with the instrumentation, or
just coincidences at a fairly implausible level. The trust of the
matter is that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 3/21/13 7:15 AM, André Warnier wrote:
> Christopher Schultz wrote:
>>
>> I think there might be a problem with the instrumentation, or
>> just coincidences at a fairly implausible level. The trust of the
>> matter is that Tomcat does not
Christopher,
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 3/20/13 2:25 PM, André Warnier wrote:
Saurabh Agrawal wrote:
All our assets are served from L3 CDN. So the asset requests
never come to the application server.
That, I do not understand. I do n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 3/20/13 2:25 PM, André Warnier wrote:
> Saurabh Agrawal wrote:
>> All our assets are served from L3 CDN. So the asset requests
>> never come to the application server.
>
> That, I do not understand. I do not understand what you mean by
>
Saurabh Agrawal wrote:
-Original Message-
From: André Warnier [mailto:a...@ice-sa.com]
Sent: Wednesday, March 20, 2013 3:27 PM
To: Tomcat Users List
Subject: Re: Tomcat Behavior on Multiple HTTP requests from same browser
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE
-Original Message-
From: André Warnier [mailto:a...@ice-sa.com]
Sent: Wednesday, March 20, 2013 3:27 PM
To: Tomcat Users List
Subject: Re: Tomcat Behavior on Multiple HTTP requests from same browser
Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash:
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Saurabh,
On 3/19/13 9:46 PM, Saurabh Agrawal wrote:
maxThreads="${tomcat.maxthreads}"
minSpareThreads="${tomcat.minsparethreads}"
maxIdleTime="${tomcat.maxidletime}"/>
port="${tomcat.ajp.port}" maxHttpHeaderSize="819
> From: Saurabh Agrawal [mailto:sagra...@sapient.com]
> Subject: RE: Tomcat Behavior on Multiple HTTP requests from same browser
> We have not set the "keep alive" explicitly in tomcat's server.xml.
It's on by default.
> s defined; are the requests coming i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Saurabh,
On 3/19/13 9:46 PM, Saurabh Agrawal wrote:
> maxThreads="${tomcat.maxthreads}"
> minSpareThreads="${tomcat.minsparethreads}"
> maxIdleTime="${tomcat.maxidletime}"/> port="${tomcat.ajp.port}" maxHttpHeaderSize="8192" maxThreads="200"
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 3/20/13 6:52 AM, André Warnier wrote:
> If I may add something : at some point, on each Tomcat server,
> there is only 1 "listening socket" for one port (the point being :
> you could have several, but you won't have 8000). So even if you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Saurabh,
On 3/20/13 3:27 AM, Saurabh Agrawal wrote:
> The point I was trying to make when I mentioned that all requests
> from the same browser results in same thread is not a mere
> coincidence. The reason why it may not be sheer luck is because
List
Subject: Re: Tomcat Behavior on Multiple HTTP requests from same browser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Saurabh,
On 3/19/13 8:55 PM, Saurabh Agrawal wrote:
> What I want to understand is if the Tomcat will keep Thread 1 as
> persistent thread to server the second reques
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 3/19/13 10:31 PM, Nick Williams wrote:
> I'm glad to see that you have a working cluster of some sorts and
> that you are performing load tests to evaluate its performance.
> This means you are on the right track, making some good decision
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Saurabh,
On 3/19/13 8:55 PM, Saurabh Agrawal wrote:
> What I want to understand is if the Tomcat will keep Thread 1 as
> persistent thread to server the second request (for login) from
> the same browser or will it assign a separate thread from the
Mark Thomas wrote:
Nick Williams wrote:
On Mar 19, 2013, at 8:49 PM, Saurabh Agrawal wrote:
Hi Nick,
We currently have 8 tomcat nodes with each node configured to have
1000 maxThreads. We did a round of performance test for 8000 concurrent
users and the observation was that the number of a
Nick Williams wrote:
>On Mar 19, 2013, at 8:49 PM, Saurabh Agrawal wrote:
>
>> Hi Nick,
>>
>> We currently have 8 tomcat nodes with each node configured to have
>1000 maxThreads. We did a round of performance test for 8000 concurrent
>users and the observation was that the number of active execu
day, March 20, 2013 2:31 AM
To: Tomcat Users List
Subject: Re: Tomcat Behavior on Multiple HTTP requests from same browser
On Mar 19, 2013, at 8:49 PM, Saurabh Agrawal wrote:
> Hi Nick,
>
> We currently have 8 tomcat nodes with each node configured to have 1000
> maxThreads. We did
; From: Nick Williams [mailto:nicho...@nicholaswilliams.net]
> Sent: Wednesday, March 20, 2013 1:44 AM
> To: Tomcat Users List
> Subject: Re: Tomcat Behavior on Multiple HTTP requests from same browser
>
>
> On Mar 19, 2013, at 8:37 PM, Caldarale, Charles R wrote:
>
&g
Williams [mailto:nicho...@nicholaswilliams.net]
Sent: Wednesday, March 20, 2013 1:44 AM
To: Tomcat Users List
Subject: Re: Tomcat Behavior on Multiple HTTP requests from same browser
On Mar 19, 2013, at 8:37 PM, Caldarale, Charles R wrote:
>> From: Saurabh Agrawal [mailto:sagra...@sapie
Saurabh Agrawal
Manager Technology | Sapient
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Wednesday, March 20, 2013 1:37 AM
To: Tomcat Users List
Subject: RE: Tomcat Behavior on Multiple HTTP requests from same browser
> From: Saurabh Agr
On Mar 19, 2013, at 8:37 PM, Caldarale, Charles R wrote:
>> From: Saurabh Agrawal [mailto:sagra...@sapient.com]
>> Subject: Tomcat Behavior on Multiple HTTP requests from same browser
>
>> Let's say I hit http://localhost:9001/homepage.html. Upon hitting the URL,
&g
> From: Saurabh Agrawal [mailto:sagra...@sapient.com]
> Subject: Tomcat Behavior on Multiple HTTP requests from same browser
> Let's say I hit http://localhost:9001/homepage.html. Upon hitting the URL,
> tomcat will assign one of the worker threads (say Thread 1) from the p
Hi,
I have tried to find the simplest of answer from so many tomcat forums but have
not got concrete answer to my query. The query I have is around management of
multiple HTTP requests triggering from same browser one after other and being
served by Tomcat container.
Let me take an example. Le
31 matches
Mail list logo
