This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Servlet specification says that Only a single instance of a servlet is created by the Container at startup time. If more than one user calls that servlet, an additional thread is created to serve the request. I just want to know that Can we limit the number of threads ? In other words If one lakh (100,000 users) access the servlet at the same time. Will one lakh threads be created. where can we specify that servlet engine can't create threads beyond a specified limit, If possible. If no, where can we specify to limit the number of threads ? Thanks in advance
Control of the number of requests that a servlet container will try to service "at one time" is what you are talking about. This varies by vendor - in Tomcat, look at the server.xml file Connector element. For example:
This says to limit the number of simultaneous requests to 75. I think the interpretation of acceptCount is that will accept that many connections but will only assign working Threads to the lesser number of 75. Bill
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Can we control number of threads of a servlet instance