Chris, thanks for the excellent feedback; thus far this list exceeds Stackoverflow by orders of magnitude ;--)
Re: ease of implementation, yes, a single instance with multiple virtual hosts is the way to go (similar setup to apache virtual hosts). However, some of the LAMP stack apps will have legacy/archived functionality that I have zero interest/time in porting over to JVM/Groovy framework. So, the plan is to mod_rewrite archived requests to php, along with static files (css,jss,html,etc.), and use Tomcat to serve up non-legacy dynamic content, connecting via AJP or mod_proxy. Amazed that you have been able to tweak JVM memory usage down to as little as 128mb, incredible. The OOME issue is a real one given my lack of experience in Java -- have @5 months Groovy under my belt and am enjoying it far too much to return to php -- so "important" client sites will have their own dedicated Tomcat instance; the rest, I'll virtual host in a single instance. Am interested in Tomcat 7's new DBCP model as well. Coupled with Groovy per request singleton (unlike per instance/application lifetime), I should be able create a db connection handle on request start and thereafter have all queries in the request run against this cached connection (could also do a true singleton, the most efficient, but as I understand, singletons are specific to the entire instance, and therefore will not work for a virtual hosts setup). Lots to learn clearly, but am loving the potential here, sky is the limit performance-wise... -- --Noah Noah Cutler Web/Mobile Applications New Mind Development ad...@newminddevelopment.com http:://newminddevelopment.com On Tue, 2011-03-15 at 16:26 -0400, Christopher Schultz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Noah, > > On 3/15/2011 2:05 PM, Noah Cutler wrote: > > Obviously per instance is a memory hungry solution, albeit highly > > convenient. Placing all sites in a single instance is a possibility as > > well (and the most resource "friendly"), but I would need to implement > > some form of load balancing for the mid-business-day client A emergency > > restart (since all sites would be affected by the restart). Of course, I > > should have load balancing for the per instance solution as well to > > ensure application uptime even on restart. > > Something else to consider is that your configuration becomes more > complicated when you decide to go to more than 1 JVM: you'll have to use > a fronting web server to determine which backend JVM to contact. > > If you have a single JVM, you can use it directly as your web server > with no other moving parts. > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk1/y2IACgkQ9CaO5/Lv0PD4MQCgkWFA858UtCfSUmR+vlmnKI1l > kwAAniGvFqVvLI4jfTJKzPEqXfyh4y05 > =zT2G > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
