Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of knst.kolinko@gmail.com
 designates 209.85.160.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <BLU162-ds17349592A08291CD68D932D3220@phx.gbl>
References: <BLU162-ds17349592A08291CD68D932D3220@phx.gbl>
Date: Fri, 20 Apr 2012 23:39:04 +0400
Message-ID: 
 <CABzHfVk9HWEFBS8b2-2MS0X4LYbD_NOn5w1ncuqWm21_PkRmbA@mail.gmail.com>
Subject: Re: catalina.out file is growing very rapidly! How to prevent
 Hibernate's INFO and DEBUG statements from getting added to catalina.out
 file?
From: Konstantin Kolinko <knst.kolinko@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2012/4/20 Dilip Shah <dilipvshah@hotmail.com>:
> The following provides clarifications / details on the environments in wh=
ich
> the application is developed and then hosted:
> (quite a bit of detail but I'm hoping this will help get to the root of t=
he
> issue)
>
> Develop environment:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> * Windows XP SP3
> * Tomcat version information:
> C:\apache-tomcat-5.5.25\bin>version
> Server version: Apache Tomcat/5.5.25
> Server built: =A0 Aug 24 2007 05:33:50
> Server number: =A05.5.25.0
> OS Name: =A0 =A0 =A0 =A0Windows XP
> OS Version: =A0 =A0 5.1
> Architecture: =A0 x86
> JVM Version: =A0 =A01.6.0_30-b12
>(...)
> Live environment:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> * CentOS release 5.4 (Final)
> Linux ip-208-109-190-155.ip.secureserver.net 2.6.18-53.el5 #1 SMP Mon Nov=
 12
> 02:22:48 EST 2007 i686 i686 i386 GNU/Linux
> * Tomcat version information:
>
> Server version: Apache Tomcat/5.5.28
> Server built: =A0 Jul 24 2009 01:33:09
> Server number: =A05.5.28.0
> OS Name: =A0 =A0 =A0 =A0Linux
> OS Version: =A0 =A0 2.6.18-53.el5
> Architecture: =A0 i386
> JVM Version: =A0 =A01.6.0_23-ea-b01
> (...)

1. This list generally does not allow attachments.

It may allow ones that have text/plain as their mime type (e.g. files
with *.txt extension), but it is nowhere written.

2. I'll comment on the files that you sent to me directly.

DevConsoleOutput.txt (that is console output on the Windows machine) contai=
ns:

[[[
[ INFO] 2012-04-20 08:55:55 (ApplicationContext.java:log:647) -
Initializing Spring root WebApplicationContext
]]]

catalina.out (from live system on CentOS) contains:
[[[
[ INFO] 2012-04-20 01:11:41 (ApplicationContext.java:log:653) -
Initializing Spring root WebApplicationContext
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/usr/java/tomcat-5.5/common/lib/logback-classic.jar!/org/slf4j/im=
pl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/usr/java/tomcat-5.5/common/lib/slf4j-log4j12-1.5.2.jar!/org/slf4=
j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explana=
tion.
]]]

Note:
1. Different source line numbers in ApplicationContext logging output.

That is - you run with different libraries in Dev vs Production.  That
is besides the different versions of Tomcat.

2. Note the SLF4J logging library complaining that you have multiple
conflicting copies of the library.

There is no such SF4J warning in your dev environment. Starting with
it your logging goes crazy.

You have some mess in your common/lib.
You'd better remove all libs that do not belong to the default Tomcat
configuration and features configured in server.xml/context.xml files
(e.g. JDBC drivers) and keep them inside of your webapp.

> Question:
> * where are the other files such as admin.2012-04-20.log, catalina.2012-0=
4-20.log, etc configured?

It is a bit complicated. In short:

1. Tomcat 5.5 -> uses Apache Common Logging library

2. Apache Common Logging library -> decides whether to use log4j or
java.util.logging (differently in each classloader, depending on what
classes are available).

3. java.util.logging  configuration is specified in
conf/logging.properties. It creates those files.

> Question:
> * who could be responsible for creating and configuring catalina.out file=
 on the Linux sever? Where do I look?

The last executed line of catalina.sh (the one that starts Tomcat)
redirects stderr and stdout streams from started java application - by
default to that file.

Best regards,
Konstantin Kolinko

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