Suppose you have a configuration like this: <VirtualHost 1.1.1.1> ServerName srva ServerAlias a.srva ServerAlias b.srva . [ some apache specific conf omitted] . <FilesMatch "/*.jsp"> JkUriSet group wrka </FilesMatch> <Location "/servlet"> JkUriSet group wrka </Location> </VirtualHost>
<VirtualHost 1.1.1.1> ServerName srvb ServerAlias a.srvb ServerAlias b.srvb . [ some apache specific conf omitted] . <FilesMatch "/*.jsp"> JkUriSet group wrkb </FilesMatch> <Location "/servlet"> JkUriSet group wrkb </Location> </VirtualHost> Mod jk2 will save the uri's only by the names written in FilesMatch and Location without the virtual server name and alias, so after reading the configuration the only save uri set is the last one that was read, as seen from jkstatus "runtime uri info": id name host uri group 0 /*.jsp srvb /*.jsp wrkb 0 /servlet srvb /servlet wrkb No mention of srva and all the requests for /*jsp and /servlet, wether sent to srva or srvb will be redirected to wrkb. There is no way ( at least no one i could figure out) to map the requests with the correct worker unless you omit completely any jk2 config from http.conf and map all the uri into workers2.properties. But this is not feasible when you have many virtual hosts with many aliases and many FilesMatch and Location, because of the explosive count of the various combinations [(Number of VirtualHosts) * (number of names for each VirtualHost) * (number of filesystems and webspace containers)] and the fact that the discrimination of the requests is delegated to mod_jk2 instead of the more efficient apache. Is this still work in progress or is a bug? Thanks, Gabriele -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>