Hola,
Numerous users/organizations have reported using Tomcat for that number of
concurrent users and higher. Achieving good and efficient programming is
usually the bottleneck. You might also want to try clustering and
load-balancing your Tomcats. If you don't want to involve Apache you can
100 concurrent users don't necessarily mean heavily loaded. Try 5000
concurrent users or something even higher. Keep in mind the
bottleneck will be your database, so try to figure what 100 concurrent
users means in terms of peak and average concurrent requests.
in other words. What are the
Also consider that using Apache 2.x is front of a farm of tomcats will
help you upgrade your configuration to handle more and more users and
requests.
For information, I'm using 2 Tomcat 3.3.2 to handle about 35
XML-RPC requests by days, Apache2 in front handling the GZIP
compression.
On
