> From: Pieter Temmerman [mailto:ptemmerman....@sadiel.es] > Subject: Recommendation # webapps > > The most logical answer would be; Use one Tomcat per webapp, whenever > possible. However, the administration overhead is so much bigger than > using a single Tomcat.
Not just administration overhead, but also that of physical resources - primarily memory. There's a lot of virtual and real memory consumption by each process, so how much RAM you have is often the limiting factor. You really don't want to get into paging in a production environment. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
