Hi Joseph, I had the same problem a while ago and never solved it. The root cause is that for whatever reason the Location-JkUriSet combination acts globally to the httpd.conf file rather than relative to the virtual host. I wasn't sure if the problem was with JkUriSet or with apache's Location directive. It sounds like it used to work for you with JkMount so the problem must be with JkUriSet...
>> Side Note << List Users, Am I correct in assuming the problem lies with JkUriSet? Has anybody gotten this to work? >> << I had to work around this by explicitly defining mappings in workers2.properties. This, of course, blows the whole concept of mass virtual hosting out of the water since you have to manually add domains to the workers2 file... Does jk work correctly in this sense, where mappings are relative to the virtual host? If so, i'm switching back... Adrian Lanning ----- Original Message ----- From: "Joseph Shraibman" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Thursday, March 18, 2004 1:49 AM Subject: how to use multiple jk2 connectors? > I have multiple ip based virtual hosts, so in tomcat I configured three > seperate engines with connectors on different ports, and in the apache > <VirtualHost> I JkMount the worker that I configured in > worker.properties to connect on a specific port. This works fine for > mod_jk, but when I try mod_jk2 it insistes on using the default host of > the engine that has the connector listening on port 8009. > > This is how I configure jk2: > <Location "/*.jsp"> > JkUriSet worker ajp13:localhost:8019 > </Location> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
