[quote]I can not understand how you can justify that doubling the Tomcat instances you can have "load balancing".[/quote] In my case Tomcat7 is reverse-proxied with Apache, this is why load-balancing could be set with a second Tomcat.
[quote]If your goal is to increase your served request rate, just work on the single tomcat config params (try to increase the maximum served connections parameters, the queues, works on timeout, parallel threads..) But if you want to be fault tolerant.. this will not save you for sure! [/quote] [quote]1) I doesn't make sense to try to load-balance the same application with two tomcats on one hardware server. One tomcat is quite capable of heavily loading the server, if you configure it property (enough RAM, enough threads, maybe look at the NIO connector). Both for load balancing and failover scenarios you really need 2 servers.[/quote] Indeed the point is to decrease response time. I believe I've already brought improvement to Tomcat like changing a bunch of its config params and setting c3p0 up for jackrabbit, but for instance increasing maxThread for Tomcat has its cost in term of server resources which I can't afford (we have s dedicated server that host many php websites), so I thought adding a second Tomcat would be a tradeoff to this limitation. [quote]Regarding your actual question: two magnolia public instances *cannot* share the same JCR repository. [/quote] You just enlighten me on the question, and many thanks [quote]So two tomcats can use the same WAR file, yes, but they need to deploy it each to their own respective appBase (="webapps") directories.[/quote] I know about this but the question was about magnolia as a web-app. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=c1bc6060-ec67-4221-a4c1-1a43ed3ec718 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
