From users-return-135599-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org Wed Nov 09 19:05:43 2005 Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 38578 invoked from network); 9 Nov 2005 19:05:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Nov 2005 19:05:43 -0000 Received: (qmail 96979 invoked by uid 500); 9 Nov 2005 19:05:28 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 96964 invoked by uid 500); 9 Nov 2005 19:05:28 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 96953 invoked by uid 99); 9 Nov 2005 19:05:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2005 11:05:28 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.135.225.68] (HELO quark.eurokom.ie) (192.135.225.68) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Nov 2005 11:05:21 -0800 Received: from HOLODECK ([192.168.225.57]) by vms.eurokom.ie (PMDF V6.2-1x9 #40199) with SMTP id <01LV7E7IOK5QDMZ4Q0@vms.eurokom.ie> for users@tomcat.apache.org; Wed, 09 Nov 2005 19:04:18 +0000 (WET) Date: Wed, 09 Nov 2005 19:04:08 +0000 From: Andoni Subject: Re: Is timestamp feature of Logger in 4.1.31 broken? To: Tomcat Users List Message-id: <001501c5e560$5ceaa5b0$39e1a8c0@HOLODECK> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Mailer: Microsoft Outlook Express 6.00.2800.1506 Content-type: multipart/alternative; boundary="Boundary_(ID_1RLRzy72LqpCU2zjgn4jng)" X-Priority: 3 X-MSMail-priority: Normal References: <000901c5e558$e64a29f0$39e1a8c0@HOLODECK> <43724546.7050201@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --Boundary_(ID_1RLRzy72LqpCU2zjgn4jng) Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 7BIT Sorry, just banging my head off the wall too much to think about things straight! Apologies to any Tomcat developers reading this! What I did was turn off time-stamp but what I was trying to do was have no date element to the logfile's *name*. I didn't realise that the timestamp="true" refers to the logged lines inside the file and not to the date element of the file name. Thanks for your help anyway Mark. Andoni. ----- Original Message ----- From: Mark Thomas Newsgroups: gmane.comp.jakarta.tomcat.user Sent: Wednesday, November 09, 2005 6:51 PM Subject: Re: Is timestamp feature of Logger in 4.1.31 broken? Andoni wrote: > Hi, > > I have just recently installed Tomcat 4.1.31 and now I find that all my log files have timestamps whether or not I have included timestamp="true" in the logger. In fact they even have it if I have specified timestamp="false" which is documented as being the default. > > Am I doing something wrong or is this a known bug in 4.1.31? Works for me. Looks like you are doing something wrong. There are loggers set at several levels in server.xml Make sure the lower level ones are set to timestamp="false" as well. Mark --Boundary_(ID_1RLRzy72LqpCU2zjgn4jng)--