We in production environment, replaced mod_jk with mod_proxy a long time ago. It performed faster and it scaled to more concurrent users. So there was no benefit to the AJP protocol. All we would like to see, is to enable load balancing on either mod_rewrite or mod_proxy, and then we have everything we want
Filip ----- Original Message ----- From: "Manni Wood" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Guenter Knauf" <[EMAIL PROTECTED]> Sent: Tuesday, July 20, 2004 10:58 AM Subject: RE: Invitation to HTTPD commiters in tomcat-dev The real trick is getting Apache to serve all of the static content, and getting tomcat to deal with only servlets and jsps. I notice in all of the documentation I find for mod_jk, an entire directory (/examples/* being everyone's favourite) is mapped to Tomcat, so that even requests for images are passed back to tomcat, rather than being taken care of Apache directly. For business sites where the entire web site is the webapp (/* in other words) apache is just passing *everything* back to tomcat, which pretty much makes one give up and serve the whole site using Tomcat, forgoing some of Apache's nicer features that have not yet been implemented in tomcat (such as mod_usertrack.) So I must stick to my argument here, and say that finding truly good documentation for mod_jk, for fine-tuned configuration, as required by the many business clients I've done work for, is difficult to impossible at this point in time. Not even O'Reilly's Tomcat book proved useful in this regard. -Manni -----Original Message----- From: Guenter Knauf [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 11:45 AM To: [EMAIL PROTECTED] Subject: RE: Invitation to HTTPD commiters in tomcat-dev Hi, > 1. Fantastic documentation. I cannot stress this enough. Hell, I'd even > volunteer for this part. The module iteself could be poorly implemented, > problematic to compile, and have truly silly defaults, but if it was > incredibly well and clearly documented, I'd use it over mod_jk2 starting > tomorrow. I agree that the docu about mod_jk2 is somewhat poor.... > 2. Barring my comments in 1, a module that really and truly works, and > has useful out-of-the-box (or freshly-compiled) defaults. (Maybe even, > by defalt, *only* passes servelt/JSP requests to tomcat, and lets Apache > handle the rest automatically.) although I'm not happy with all defaults of mod_jk2, I think you can very simply get the base connection to Tomcat up; we started with a simple how-to for NetWare, and later coned it for Win32 (tehse are both typical binary consument platforms where admins usually do not have such an insight as perhaps Unix admins): http://www.gknw.com/development/apache/docs/win32/mod_jk2/ if you look at the to ways we mentioned you can see that it's not so hard to get mod_jk2 up than you might think... f.e. if you rename this to workers2.properties: http://www.gknw.com/development/apache/docs/win32/mod_jk2/min_w2.propert ies and put it into your apache2 conf dir then mod_jk2 will pick that up automatically without further config, and you should already be able to browse Tomcat samples or docu though the connector... can this be more simple?? Guenter.
