Tomcat hangs up ... Huge count of webapps
Hi everybody and java experts, i have a huge count of webapps (approximately 25) in my Tomcat here, running on Suse Linux 9.1. After a few connection requests, Tomcat just hangs up and doesn't accept anymore connections. I can't kill the process anyway, only "killall -9 java" helps. 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. Question is: what is the maximum count of webapps, Tomcat is able to handle? Or are there any other configuration hints? System is - Suse Linux 9.1 - 2GB of RAM - 3.0 Ghz Machine - JDK1.4.2_06 and JRE1.4.2_05 (same effect on every Java version) - Tomcat 4.1.31 or Tomcat bundle with TDK-2.2 (TurbineDevelopmentKit) .. This is an absolut urgent issue! Please reply asap .. Thx a lot Regard, Martin Eberle
RE: Tomcat hangs up ... Huge count of webapps
Hi, >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. >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. >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. >Or are there any other configuration hints? Only the usual: think and apply performance testing principles. There's no magic switch or configuration. In your case, you probably want to split the apps into multiple Tomcat servers, and profile each app (or small set of apps) separately to determine its hardware and memory requirements. Then figured out how you want to use your hardware and configure as many instances of Tomcat as you need. >- JDK1.4.2_06 and JRE1.4.2_05 (same effect on every Java version) Those two versions are not that different ;) It might be worth your time to try J2SE 5.0, JRockit, or other JVMs. >This is an absolut urgent issue! Please reply asap .. Thx a lot Then you're SOL for now ;) It's no fun doing capacity planning after deployment, and there are no easy shortcuts ;( Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Tomcat hangs up ... Huge count of webapps
>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]
RE: Tomcat hangs up ... Huge count of webapps
Hi, >### Ok. It's not THAT huge .. but we have ~45 users per webapp which are >going to connect on nearly the same time .. 25 apps * 45 users = virtually 1125 concurrent users, that's significant. > I'm bringing up the JVM with /usr/j2re142_05/bin/java -server >-Xmx1024m -Xms256m -D ... Then it's not allocating 1.96GB: how did you get that number for your original post? >>> 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 :( SOL: www.acronymfinder.com/default.asp?p=dict&String=exact&Acronym=SOL. Tomcat has only improved in terms of memory usage, stability, and performance over time. It's more likely that your apps, your load, your hardware, or a combination of the above have changed. Regardless, this is why you should also stress-test your applications as they would be deployed in production against the expected user load. For now, you should probably split the apps into multiple Tomcat instances running on separate servers. That way would reduce the load, reduce the JVM size, and increase the performance seen by your users. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
