FYI .... > [EMAIL PROTECTED] wrote: >> Well, i rechecked all twice, i't a new fresh install. >> The only old thing is the app context, that is not embedded into server.xml >> but as a standalone file. >> I still had a doubt about the jk module that was compiled for 4.1.10, but i >> downloaded 4.1.12 connectors and recompiled them. >> I tested both jk and jk2 with ajp3 connector with same results. >> Also the application was recompiled against 4.1.12. >> If nobody has any other hint, i'll open a bug. > > According to my testing, this doesn't happen with Tomcat standalone on > 8080 (or you'll have to explain how to get the problems). > > Since the requestURI buffer isn't used much in Tomcat, it is possible > that Coyote JK2 mutates it, creating the incorrect logs.
I have a filter that calls request.getRequestURI() after the request has been processed by the destination servlet. (The filter roughly measures servlet processing times). When I changed from using mod_jk to mod_jk2, request.getRequestURI() started returning part of the content of the response instead of the URI. Moving the call to request.getRequestURI() before the call to chain.doFilter() fixed the problem. This didn't happen with mod_jk or the http connector. > Of course, if you use Apache + Tomcat, maybe you should use the native > access logger instead (it should be much faster). > > Remy > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
