posted 22 years ago
"connected" is a dangerous term. Since HTTP is a transactional protocol, you won't be consuming large amounts of network resources unless you have big data transfers and/or lots of concurrent activity, where the network bandwidth and CPU are likely to be the limiting factor.
Of course, one type of "connection" is the server-side session information, which may be anything from nothing to huge (well, try to avoid huge), depending on your design. It's always best to keep this light, in which case 100 of them isn't likely to be a problem.
There are no hard-coded limits in Tomcat for most of this, except for things like maximum simultaneous connections (NOT session connections - we're talking actual in-progress HTTP requests), sizes of resource pools, and such, which are used mostly for tuning.
Whether 100 users is a burden depends on your server and the way the app is written. It's not a bad idea to set up some benchmarks and stress tests.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.