Thanks again for your insight into the problem.

Following your advice, I started from a fresh install of Tomcat 5.5.33.
I noticed that log4j.1.2.16.jar is included in the common/lib folder by
default.

The only modification I made was the small addition to logging.properties:

        org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level
= INFO
        
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].handlers =
1catalina.org.apache.juli.FileHandler

I experienced the same results:
        - on first run, everything is fine but logs are empty.
        - second run I removed the log4j jar file
        - Tomcat now produces the output in the log files, but now complains
several times about ClassDefNotFound for log4j

Cheers,

Brian J.


-----Original Message-----
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] 
Sent: Friday, October 21, 2011 2:24 PM
To: Tomcat Users List
Subject: Re: Tomcat produces empty/missing log files

2011/10/21 Brian Jones <bjone...@uwo.ca>:
>
>        It would be nice to see the actual command line that starts
Tomcat's
> Bootstrap. The JVM keys that configure  java.util.logging should be there.
>
> - I don't know what you mean by this.
>

I mean catalina.bat purpose is to prepare and call "java.exe". I'd
like to see the real command line that starts "java.exe".


> o   Followed instructions at
> http://tomcat.apache.org/tomcat-5.5-doc/logging.html to set up logging
>
>        Maybe 7.0 docs will be more understandable.
>
> - 7.0 docs are not applicable, as I'm dealing with v5.5.33, and cannot
> upgrade to newer versions of Tomcat because 5.5.33 is the only version
> supported by the software project I'm working on (as stated in previous
> message)

Have you tried reading them? I spent good time trying to improve those
docs, to better explain what is going on, but wouldn't backport those
to 5.5.x


>
> - Yes, restored to original configuration. If I remove the log4j-x.x.x.jar
> file, it will then throw multiple exceptions like
> "java.lang.NoClassDefFoundError: org/apache/log4j/Priority" while starting
> Tomcat

??? What throws it?
There should be a stacktrace.


Maybe you shall start with a fresh copy of 5.5.33?

>
> o  Contents of logging.properties file (located in BOTH /common/classes/
and
> /conf/ folders):
>
>        It should be only in conf.
>
> - The instructions at http://tomcat.apache.org/tomcat-5.5-doc/logging.html
> clearly state that the file is "to be placed in common/classes".

Huh. The doc is wrong there.

The file in common/classes will take priority over the one in conf,
but I'd say that that is an unusual configuration.

> Even so, I
> removed it from that directory, but get the same result
>
>        "Try to simplify your configuration.":
>
> - following your instructions I simplified the logging.properties file to
> the 1 entry you suggested. This produced some confusing results. The log
> file now contains MOST of the output; some exceptions found in the log;
the
> console was empty, but one exception was logged in the console and not in
> the log file.

Which one?

> Ideally (and what I think is normal behavior for Tomcat) it
> should be putting all output to the console, and duplicating all output to
> the log file.

In production you wouldn't want that output on console. It is harder
to rotate catalina.out.

>
> - I then did another experiment, keeping the more verbose
logging.properties
> file, and adding the following:
>
>        org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level
> = INFO
>
> org.apache.catalina.core.ContainerBase.[Catalina].[localhost].handlers =
> 1catalina.org.apache.juli.FileHandler
>
> - With this change, I can see all output in the console, and I can see
that
> it's now putting some of the output in two different files,
> catalina.date.log and localhost.date.log

http://www.catb.org/~esr/faqs/smart-questions.html

What is those "verbose logging.properties" and why those lines? You
are asking something, but are not providing facts. Do you expect
guesses as an answer?


Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to