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. 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 request which will be processed and then response 
will be sent to the client. Now if I hit a link on homepage which is for login, 
a separate HTTP request will be initiated from the same browser.

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 pool ?

If I look at my server logs for both the requests from client, the thread id 
remains the same which gives me a feeling the state of HTTP is persistent and 
till the time browser is not closed, the thread won't be returned to the pool.

Please can someone clarify the above behavior.

Note: I need to configure the maxThreads setting of Tomcat to support 20,000 
concurrent users in the system. The above clarification will help me pick the 
appropriate setting for maxThreads.

Saurabh Agrawal
Manager Technology | Sapient

Aachvis Softech Private Limited SEZ,
"Oxygen", (Tower C), Ground - 3rd Floor,
Plot No. 7, Sector 144 Expressway,
Noida 201 301
Uttar Pradesh, India

Tel: +91 (120) 479 5000
Mobile: +91 981 866 4383
Fax: +91 (120) 479 5001
Email: sagra...@sapient.com<mailto:sagra...@sapient.com>

sapient.com

The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender and delete the material from any (your) computer.

***Please consider the environment before printing this email.***

Reply via email to