mod_jk supports load balancing across several tomcat servers and also supports serving static content from Apache and *.jsp from tomcat.
mod_webapp does not support load balancing, and the decision to forward requests to tomcat are based on whole directories, you cannot use wildcards such as *.jsp I believe that the official stance is that mod_webapp will be the future of Apache-tomcat connectors, and it will receive performance and feature improvements whereas mod_jk represents a connector that works pretty well in the meantime. I personnally use mod_jk for a site that receives 2M hits per day without a problem. I would recommend mod_webapp if you do not need load balancing and if your static content is in a different directory than your JSP and web apps. And if you need load balancing, go with mod_jk. mod_webapp was also notoriously broken on the Windows platform four months ago, but today I don't know. You might want to try both and decide on the one that works best for you. Good Luck, Pascal Forget Cynthia Jeness wrote: >I searched the Tomcat and Apache site yesterday for some explanation >and/or recommendations for the choice of connector, but a search on >"connector" or "mod_webapp" did not seem to provide any information >about why I would chooce one over another. Can someone point me to the >correct place or explain the difference between these connectors. > >Thanks, > >Cynthia Jeness > > >-- >To unsubscribe: <mailto:[EMAIL PROTECTED]> >For additional commands: <mailto:[EMAIL PROTECTED]> >Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
