When using the latest mod_jk2 built from source, most URL mount methods don't work properly anymore (they last did with jakarta-tomcat-connectors-4.1.24-src.tar.gz, tomcat-connectors-1.1M1-src.tar.gz and latest CVS Snapshot jakarta-tomcat-connectors_20030721044600.tar.gz are broken for that) (Apache 2.0.47, Tomcat 4.1.24) ================================================================ workers2.properties URL configuration: [uri:host.domain.cc/examples/*] group=lb:lb_test -> works only for /examples/, NOT for suburls (e.g. /examples/jsp/) (Apache 404) ssl.conf - tried all of the following configurations in SSL vhost: JkSet uri:host.domain.cc/examples/*.group lb:lb_test JkSet uri:host.domain.cc/examples/*.group ajp13:unixsocket_test_0 JkSet uri:host.domain.cc:443/examples/*.group lb:lb_test <Location "/examples/*> JkUriSet group lb:lb_test </Location> -> they all work only for /examples/, and NOT for suburls (e.g. /examples/jsp/) (Apache 404) <LocationMatch "/examples/*"> JkUriSet group lb:lb_test </LocationMatch> -> works for examples and subdirectories However with several LocationMatch/JkUriSet entries Apache error_log gets flooded with messages like this (even with jk2 logger.level=EMERG): Merging /examples2/* /examples/* /examples2/* Configuration in httpd.conf: <LocationMatch "/examples/*"> JkUriSet group lb:lb_test </LocationMatch> <LocationMatch "/examples2/*"> JkUriSet group lb:lb_test_2 </LocationMatch>
As of November 15, 2004, JK2 is no longer supported. All bugs related to JK2 will be marked as WONTFIX. In its place, some of its features have been backported to jk1. Most of those features will be seen in 1.2.7, which is slated for release on November 30th, 2004. Another alternative is the ajp addition to mod_proxy which will be part of apache 2. For more information on the Tomat connectors docs at http://jakarta.apache.org/tomcat/connectors-doc/