>i have a huge count of webapps (approximately 25) in my Tomcat here, I wouldn't classify 25 as huge, but I suppose that's subjective. We have servers running that many webapps, but they're small webapps.
### Ok. It's not THAT huge .. but we have ~45 users per webapp which are going to connect on nearly the same time .. >Well, beneath the fact that my server has 2 gigabytes of ram, only 40MB >are available after starting tomcat. So, tomcat allocates 1.96 gigabytes >of ram. You control the JVM; if it allocates 1.96GB it means you gave it -Xmx2G *at least*. Even if that's the case on purpose, you need to redesign your deployment practice because leaving 40MB free on a 2GB server will only lead to bad things. #### I'm bringing up the JVM with /usr/j2re142_05/bin/java -server -Xmx1024m -Xms256m -D ... >Question is: what is the maximum count of webapps, Tomcat is able to >handle? It's limited by your environment and requirements. Tomcat imposes no limit of its own. I ran a load test a year or so ago with 100 webapps deployed, and it worked (with good response times and CPU usage), but the apps were small and the machine was massive. Then you're SOL for now ;) It's no fun doing capacity planning after deployment, and there are no easy shortcuts ;( >> What's SOL? We didn't expect to get THAT massive problems with tomcat as i know that tomcat run even better some time ago :( --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
