Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 31842 invoked from network); 26 Sep 2002 15:04:15 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 26 Sep 2002 15:04:15 -0000 Received: (qmail 13855 invoked by uid 97); 26 Sep 2002 15:04:17 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 13839 invoked by uid 97); 26 Sep 2002 15:04:16 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 13827 invoked by uid 98); 26 Sep 2002 15:04:16 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) X-Zen-Trace: 62.3.64.112 From: "Christopher Watson" To: "Tomcat Users List" Subject: RE: Tomcat 4.1.12: access log corrupted Date: Thu, 26 Sep 2002 16:02:28 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello Reading this message had me very worried, BUT Just to let you know I DON'T get this bad behaviour. I did have to uncomment the access log valve, but it behaves OK Both as port 8080 and via IIS using tomcat's ISAPI using ajp13 port 8009 I wonder if you are using a different connector ..? Also, have you upgraded everything? Made sure all the jars are up-to-date? Cleared out the work directory Hope this helps Christopher > -----Original Message----- > From: Miguel Angel Mulero Martinez > [mailto:miguel-angel.mulero@mad.tecsidel.es] > Sent: 26 September 2002 12:49 > To: Tomcat Users List > Subject: RE: Tomcat 4.1.12: access log corrupted > > > I had look at my server.xml and it don't have a valve access log > by default > (I think remember older versions have it). I add one like yours, > and I have > got the same problem. Look at the first characters of each line: > > > >