Marcel St�r wrote: > "Bill Barker" <[EMAIL PROTECTED]> schrieb im Newsbeitrag > news:<[EMAIL PROTECTED]>... >> I don't know of any problems with the Ajp12Connector (other than the >> fact that it is old :). It looks like it should get the query string >> from Apache fine. I also can't see why the request isn't showing up >> in the Tomcat access-log.Of course, AccessLogInterceptor doesn't >> flush it's output by default, but I'm assuming that's not the >> problem. >> >> About the only thing I can suggest is to enable the LogEvents >> element in server.xml. This will give you way more information than >> you usually want, but it may include something that will show what >> the problem is. >> >> The Ajp13 protocol is better tested with TC 3.3, so if it's not too >> radical, you might also try switching mod_jk to Ajp13. > > Ok, all I would have to do, is to enable Ajp13 in server.xml (usually > port 8009) and to update my workers.properties (remove Ajp12 from > workers list), right?
Switching from Ajp12 to Ajp13 did indeed solve the problem. Many thanks to you Bill. Regards, Marcel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
