Re: How many concurrent user on Tomcat and Apache(New Bie)
You only need one workers.properties file. All it does is tell mod_jk.so where to find Tomcat. Regarding how many concurrent users that is impossible to say. It depends on what your definition of good hardware is, as well as the complexity and quality of the web applications you're hosting. It doesn't matter how much hardware you have or how many users you have, a single poorly designed web application can bring even the most robust server to a halt. John Sachin wrote: Can any body tell me that on a Apache web Server(tomcat as worker) hosting web site. How many concurrent user possible if Server has good hardware configuration. Do we need to maintains worker.properties file for many tomcat Instances under Apache.. If any body help me or any suggesstion Thanks Sachin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How many concurrent user on Tomcat and Apache(New Bie)
Hi John, But john i have to deploy my applciation for client now client is ready for each hardware And my appication performance is good. Bu My Client is saying 10,000 concurrent user.. I have found in forum archive that people suffering from problem of concurrency when concurrent user become new 1000 Well my applciation basically handling serveral temporary XML files and at last update data into database. XML file documents. created by application is nearly 2-3 kb But i am not able to judge that what approach should i follow. Well i am thinking that worker.properties file will manage load balancing between several tomcat which work as a worker under Apache So how will i judge that how many tomcat or there is no need for multiple If ant suggesstion then please let me know?? tnanks sachin -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Friday, July 25, 2003 6:03 PM To: Tomcat Users List Subject: Re: How many concurrent user on Tomcat and Apache(New Bie) You only need one workers.properties file. All it does is tell mod_jk.so where to find Tomcat. Regarding how many concurrent users that is impossible to say. It depends on what your definition of good hardware is, as well as the complexity and quality of the web applications you're hosting. It doesn't matter how much hardware you have or how many users you have, a single poorly designed web application can bring even the most robust server to a halt. John Sachin wrote: Can any body tell me that on a Apache web Server(tomcat as worker) hosting web site. How many concurrent user possible if Server has good hardware configuration. Do we need to maintains worker.properties file for many tomcat Instances under Apache.. If any body help me or any suggesstion Thanks Sachin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How many concurrent user on Tomcat and Apache(New Bie)
Suggestion: build a test environment and test. You can't wing it. John Sachin wrote: Hi John, But john i have to deploy my applciation for client now client is ready for each hardware And my appication performance is good. Bu My Client is saying 10,000 concurrent user.. I have found in forum archive that people suffering from problem of concurrency when concurrent user become new 1000 Well my applciation basically handling serveral temporary XML files and at last update data into database. XML file documents. created by application is nearly 2-3 kb But i am not able to judge that what approach should i follow. Well i am thinking that worker.properties file will manage load balancing between several tomcat which work as a worker under Apache So how will i judge that how many tomcat or there is no need for multiple If ant suggesstion then please let me know?? tnanks sachin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]