File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Servlets and the fly likes Servlet HTTP client requests Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "Servlet HTTP client requests" Watch "Servlet HTTP client requests" New topic

Servlet HTTP client requests

Ryan McClain
Ranch Hand

Joined: Nov 27, 2010
Posts: 145
1) What is the ideal methodology for handling client HTTP requests coming in for a servlet?
- Using Threads?
a) -> Is it not resource-heavy to have a million clients do a million requests at a time?
b) -> Does this only lightly affect the CPU/memory/stability on the server?
c) -> What methodology is used in real-world applications?
Ulf Dittmer

Joined: Mar 22, 2005
Posts: 42965
I'm not sure I understand the question. A servlet container does use threads, one per request. I recall reading about tests that showed that a single Tomcat instance using the NIO connector is able to handle thousands of requests per second (actually something between 10000 and 20000, if memory serves). If you need to be able to handle a million simultaneous requests that do a significant amount of work (like serious computation or accessing some other machine like a DB), you'll probably want to put in place a few hundred load-balanced machines.
Ryan McClain
Ranch Hand

Joined: Nov 27, 2010
Posts: 145
Hm, sounds interesting. Thanks
Paul Clapham

Joined: Oct 14, 2005
Posts: 19973

In real-world applications the usual thing to do is just to use a servlet container such as Tomcat or Websphere. The situation where you have a million requests at the same time is highly unusual.
I agree. Here's the link:
subject: Servlet HTTP client requests
It's not a secret anymore!