Some of actually use both logs(apache and tomcat) for varios reasons. The tomcat logs allow us to look at how well load balancing is working across all our tomcat instances.
If bug patch 12145 were examined - tomcat logging would be much richer allowing Request & Session Attributes, Cookies, and Input Headers to also be logged per request. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12145 Remy Maucherat wrote: > [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. > 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]>
