You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/11/22 23:27:26 UTC

DO NOT REPLY [Bug 14784] New: - access log garbled

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14784>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14784

access log garbled

           Summary: access log garbled
           Product: Tomcat 4
           Version: 4.1.12
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: scott@xigole.com


The access log for any virtual host is garbled.  I have 12 virtual hosts defined
and all of their access logs are of no real value.  The other logs are fine.  A
sameple host configuration:

<Host name="www.myhostnamehere.com" debug="100"
      appBase="/home/tomcat/sites/myhostnamehere.com" unpackWARs="true">

    <Alias>myhostnamehere.com</Alias>

    <Valve className="org.apache.catalina.valves.AccessLogValve"
           directory="logs" prefix="myhostnamehere.com_access_log."
           suffix=".txt" pattern="common"/>

    <Logger className="org.apache.catalina.logger.FileLogger"
            directory="logs" prefix="myhostnamehere.com_log." suffix=".txt"
            timestamp="true"/>

    <Context path="/manager" docBase="manager"
             debug="0" privileged="true"/>

    <Context path="" docBase="" debug="100"/>

</Host>

Version info:
Tomcat: Apache Tomcat/4.1.12
JDK: 1.4.1_01-b01 Sun Microsystems Inc.
O/S: Linux 2.4.18-18.7.x i386 (RedHat 7.2)

Tomcat is fronted by Apache HTTPD 1.3.27 with mod_jk 1.2.1-beta-1

I'm setting this to major as it is impossible to get anything useful from the
access logs.

On some of the sites that display the problem the only thing on the site is a
single index.jsp that contains:

<%
    response.sendRedirect( response.encodeRedirectURL(
"http://www.therealsite.com/" ) );
%>

yet these sites still have an access file that looks like

 Tomcat/4.1. - - [22/Nov/2002:13:49:33 -0800] "HEAD <title>Apa HTTP/1.1" 302 -
 Tomcat/4.1.12 - - [22/Nov/2002:14:20:47 -0800] "GET <title>Apa HTTP/1.1" 302 -

This is actually better than some.  On some sites that contain alot of Tomcat
served content I have logs like:

002</p></td - - [21/Nov/2002:10:06:50 -0800] "GET /aboutus/index.jsp HTTP/1.1" 200 -
FFFFF">
    <t - - [21/Nov/2002:10:16:38 -0800] "POST /index.jsp HTTP/1.1" 200 -
002</p></td - - [21/Nov/2002:10:16:40 -0800] "GET /aboutus/index.jsp HTTP/1.1" 200 -
e>^M
^M<!--   - - [21/Nov/2002:10:16:45 -0800] "GET /aboutus/industrynews.jsp
HTTP/1.1" 200 -
td>
                    <t - - [21/Nov/2002:10:16:46 -0800] "GET
/aboutus/partners.jsp HTTP/1.1" 200 -
   END:     - - [21/Nov/2002:10:16:48 -0800] "GET /aboutus/press.jsp HTTP/1.1" 200 -
ble>^M
^M<!-- - - [21/Nov/2002:10:16:50 -0800] "GET /aboutus/whitepapers.jsp HTTP/1.1"
200 -

Basically just bits and pieces of requests and responses.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>