Return-Path: <Jason.Pell@dssonline.com.au>
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 88202 invoked from network); 1 Feb 2001 01:07:12 -0000
Received: from hestia.its.deakin.edu.au (root@128.184.136.2)
  by h31.sny.collab.net with SMTP; 1 Feb 2001 01:07:12 -0000
Received: from dssonline.com.au (128-184-134-190.its.deakin.edu.au
 [128.184.134.190])
	by hestia.its.deakin.edu.au (8.11.1/8.10.0) with ESMTP id f1117Dg19303
	for <tomcat-user@jakarta.apache.org>; Thu, 1 Feb 2001 12:07:13 +1100 (EST)
Message-ID: <3A78B744.2EE1AFC9@dssonline.com.au>
Date: Thu, 01 Feb 2001 12:09:24 +1100
From: Jason Pell <Jason.Pell@dssonline.com.au>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: tomcat-user@jakarta.apache.org
Subject: Re: log files in tomcat
References: 
 <D4D2B55E7576D411B04000508BE343DC028BA187@corlsmxsusr01.escout.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

I have also had problems with this.

As suggested I tried adding jvm.stderr and jvm.stdout logs to server.xml:

----------------------------------------- server.xml fragment
-------------------------------
<Logger name="jvm.stderr"
            verbosityLevel = "DEBUG"
            path="logs/stderr.log"
    />

    <Logger name="jvm.stdout"
            verbosityLevel = "DEBUG"
            path="logs/stdout.log"
    />
----------------------------------------- server.xml fragment
-------------------------------

But no joy I am afraid.  Is this the correct config info.

I am running Tomcat 3.2.1 on Redhat 6.2

Thanks
Jason

"Garmaev, Vladimir A" wrote:

> There should be two more logs:
>
> jvm.stderr
> jvm.stdout
>
> The latter is logging System.out.println
>
> -----Original Message-----
> From: Ross Manges [mailto:rdawggg@yahoo.com]
> Sent: Wednesday, January 31, 2001 1:44 PM
> To: tomcat-user@jakarta.apache.org
> Subject: log files in tomcat
>
> Hello folks,
>
> I apologize in advance for this dumb question, but I'm
> having an exteremly difficult time getting tomcat to
> create a log file containing the event traces (and
> possibly System.out.println()'s?) from my servlets.
> I've read up on the available faq's and other
> documentation, which directs me to the server.xml
> file.  I've set that file to maximum debugging mode,
> but still no luck.  I get two files in my /log
> directory: jasper.log and servlet.log.  The latter
> contains nearly nothing, and jasper.log simply reports
> on my jsp files.
>
> Can somebody PLEASE point me in the right direction?
> If I've missed some important set of documentation
> please let me know.
>
> Thanks!
>
> --Ross
>
> p.s. - I'm running tomcat 3.2.1 standalone on WinMe,
> PIII-700, 128mb ram.
>
> __________________________________________________
> Get personalized email addresses from Yahoo! Mail - only $35
> a year!  http://personal.mail.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-user-help@jakarta.apache.org

--
Jason Pell
Senior Analyst/Programmer - Web Developer
Deakin Software Services Pty Ltd
12 Gheringhap St, Geelong Victoria 3220 Australia
Phone: 03 5227 8858 International: +61 3 5227 8858
Fax: 03 5227 8907 International: +61 3 5227 8907
E-mail Jason.Pell@dssonline.com.au
http://www.dssonline.com.au
Customer Support Hotline: 1800 620 497

"Callista - the brightest solution in university management"

---------------------------------------------------------------
Important Notice: The contents of this email transmission,
including attachments, may be privileged and confidential.
Any unauthorised use of the contents is expressly prohibited.
If you have received this transmission in error, please advise
the sender by return email or telephone immediately and
destroy all versions.
---------------------------------------------------------------