When JK2 was stopped, it was said that all major functions will be backported to JK1. We set up a huge environment (Clustered IIS and Clustered TCs) based on JK2. But one of the major enhancements in JK2 for the IIS has been forgotten so we can't join you lot on the JK1 - and I guess we are not the only ones. In JK2, you could map an real URL in the URI-Mappings, including VHost-Name: [URI:my.webname.de/tomcatapp/*] ... In JK1, it still gives an error when you try a full URL: my.webname.de/tomcatapp/*=wlb because you explicitly forbid that in the JK: if (*uri != '/') { jk_log(l, JK_LOG_WARNING, "Uri %s is invalid. Uri must start with /", uri); JK_TRACE_EXIT(l); return NULL; } Why is that? The JK2 had no problem doing that. We need that function because we have some 40-60 VHOSTS on our Webservercluster, and we do not want global Tomcat mappings - only for VHosts and contexts we name. In the file the dev even say: # The general syntax for this file is: # [URL]=[Worker name] but a URL is not possible to use, so it must be an error. I know it is now possible to use a properties file for configuration and have a config per VHost that way, but this would be a administration nightmare with our webfarm size. Please backport this feature / bugfix this issue soon.
I suspect that you should look to mod_proxy_ajp in Apache 2.2. Since it is out I suspect work on mod_jk will be primarily "as needed" maintenance and bug fixing. I could be wrong, of course.
I'd like to do that, but this bug referes to Microsoft IIS 6 like in isapi_redirect.dll instead of apaches mod_*.
Ah, I missed the "uriworkermap.properties" bit. Sorry. isapi_redirect.dll seems to be the stepchild no one wants. There are those (including me) that are very dependent on there being a high quality IIS/Tomcat connector, but even amongst those in this boat no one has any love for IIS, ISAPI, etc. Personally, I'd love it if my customers would just drop IIS and use Apache (which we bundle), but some of them are rather stubborn on this point...
JK 1.2 already supports that for qute some time (forever). Just prefix the URL with '/': /my.webname.de/tomcatapp/*
@ Jess Holle: > isapi_redirect.dll seems to be the stepchild no one wants. yes, I got that feeling too. poor kid. > Personally, I'd love it if my customers would just drop IIS and use > Apache (which we bundle), but some of them are rather stubborn on > this point... well, Apache has advantages, IIS other. I work with both and IIS6 is realy was better then the versions before. Hard to say which is better. But we do professional IT services, so we serve whatever the paying customer demands. If it's ASP or similar combined with Java, its IIS. If plain Java, Apache & Tomcat is the way. @ Mladen Turk: Is that really so? Where is that documented? We searched for quite some time. We spend many weeks developing and bugfixing the JK2 after it was discontinued because we thought we couldn't use JK1. If that Syntax realy works as expected, please add it to some docu and the sample "uriworkermap.properties". That would surely help some people out there. Everyone who depends on doing Microsoft stuff in ASP together with the power of Java in webapps need a IIS- TomCat combination.
The feature has been added to the docs in the meantime, see http://tomcat.apache.org/connectors-doc/reference/uriworkermap.html