Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of david.blevins@visi.com
 designates 208.42.176.213 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <46AFA92D.2070106@kippdata.de>
References: <D69591CE-F4AE-41EE-89B6-3DAC6220E9D7@visi.com>
 <46AFA92D.2070106@kippdata.de>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <491FE705-7075-43C7-A13A-DABF886E486A@visi.com>
Content-Transfer-Encoding: quoted-printable
From: David Blevins <david.blevins@visi.com>
Subject: Re: Juli/Logging
Date: Tue, 31 Jul 2007 19:47:10 -0700
To: "Tomcat Developers List" <dev@tomcat.apache.org>


On Jul 31, 2007, at 2:27 PM, Rainer Jung wrote:

> Hi David,
>
> our default bundled JULI only has a binding for java.util.logging. On
>
> http://tomcat.apache.org/tomcat-6.0-doc/extras.html
>
> there is a very short description, how one builds a JULI, that is =20
> log4j enabled. The static binding was chosen, because commons-=20
> logging auto detection provided to many problems w.r.t. =20
> redeployment and classloader leaks.

Cool, thanks.

> My personal opinion: java.util.logging very much lacks a good =20
> formatter. The default 2 line formatting of messages, splitting =20
> timestamps and message in separate lines, is not really useful in =20
> production. Many ad hoc log analysis practices work on a line =20
> oriented basis.

Was wondering about that.  I've heard people grumble about =20
java.util.logging, but haven't (till now) heard anything specific.  =20
Maybe I wasn't paying close enough attention, but the Tomcat 6 log =20
files still seem to follow the one line per message format.  How did =20
you pull that off?

-David

>
> Regards,
>
> Rainer
>
> David Blevins wrote:
>> So another topic,
>> There's a thread going on in OpenEJB at the moment about possibly =20
>> switching away from log4j for the reason that the logging config =20
>> gets easily messed up in embedded environments (maven, =20
>> specificaly) and of course to have one less dependency -- the 3.0 =20
>> server is a bit beefier than the 1.0.
>> I remembered not seeing log4j or commons logging in Tomcat 6 and =20
>> started investigating -- how I discovered the inlining.  Seems =20
>> juli is a trimmed down version of commons-logging (attractive), =20
>> but it isn't obvious what's driving the actual logging.  Didn't =20
>> see any inlined log4j classes.  Are you using java.util.Logging or =20=

>> something else?
>> Also noticed the javadoc of juli says it allows for per-=20
>> classloader configuration of logging.  What exactly does that mean?
>> Thanks!
>> -David
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: dev-help@tomcat.apache.org
>
> --=20
> --
> kippdata
> informationstechnologie GmbH   Tel: 0228 98549 -0
> Bornheimer Str. 33a            Fax: 0228 98549 -50
> 53111 Bonn                     www.kippdata.de
>
> HRB 8018 Amtsgericht Bonn / USt.-IdNr. DE 196 457 417
> Gesch=E4ftsf=FChrer: Dr. Thomas H=F6fer, Rainer Jung, Sven Maurmann
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
> kippdata
> informationstechnologie GmbH   Tel: +49 228 98549 -0
> Bornheimer Str. 33a            Fax: +49 228 98549 -50
> D-53111 Bonn                   www.kippdata.de
>
> HRB 8018 Amtsgericht Bonn / USt.-IdNr. DE 196 457 417
> Gesch=E4ftsf=FChrer: Dr. Thomas H=F6fer, Rainer Jung, Sven Maurmann
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>


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