-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,
>> tomcat will assign one of t
> 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 pool
> to the HTTP requ
19 matches
Mail list logo
