-----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: SHA256
>
> Saurabh,
>
> On 3/19/13 9:46 PM, Saurabh Agrawal wrote:
>> <Executor name="hybrisExecutor" namePrefix="hybrisHTTP"
>> maxThreads="${tomcat.maxthreads}"
>> minSpareThreads="${tomcat.minsparethreads}"
>> maxIdleTime="${tomcat.maxidletime}"/> <Connector
>> port="${tomcat.ajp.port}" maxHttpHeaderSize="8192" maxThreads="200"
>> protocol="org.apache.coyote.ajp.AjpProtocol"
>> executor="hybrisExecutor" enableLookups="false" acceptCount="100"
>> connectionTimeout="20000" URIEncoding="UTF-8"
>> disableUploadTimeout="true" />
>>
>> <Connector port="${tomcat.http.port}" maxHttpHeaderSize="8192"
>> maxThreads="${tomcat.maxthreads}"
>> protocol="org.apache.coyote.http11.Http11Protocol"
>> executor="hybrisExecutor" enableLookups="false" acceptCount="100"
>> connectionTimeout="20000" URIEncoding="UTF-8"
>> disableUploadTimeout="true" />
>
> Note that your <Executor> has maxThreads="200" and your <Connector>
> uses that <Executor>: your ${tomcat.maxthreads} is being ignored.
>
That, and the default keepalive setting, are probably the keys here.
And the observation of Chuck about the HTTP and AJP connectors. Over which
Connector do
the test requests actually come in ?
Saurabh - The actual front end requests come on AJP port. We are using AJP
protocol for communication between Apache and Tomcat. It helps in load
balancing across the application servers in cluster. There is a separate
internal application (not exposed on internet) used by CMS team which is using
HTTP connector. I hope that clarifies.
And a question : is the "simulation" with the 10000 clients really comparable
to what you
expect in the reality ? For example, if the simulation requests one page per
client, and
then does nothing else with that page; but the real clients would get a page,
and then
immediately request the 50 thumbnail images referenced by that page, conditions
would be
really different, and keepalive would have a very different effect.
Saurabh - The way we have configured our user journeys are as follows:
User 1: Hits homepage, clicks football link on home page, makes a selection,
adds to cart and checkout. So this is one user journey which triggers multiple
requests. All our assets are served from L3 CDN. So the asset requests never
come to the application server. We have not set keep alive explicitly anywhere
in tomcat.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
