[slf4j-user] jcl104-over-slf4j on the web's classpath causes redirection of tomcat's internal logging

Szel, Zoltan (IT) Zoli.Szel at MorganStanley.com
Tue Sep 23 17:17:03 CEST 2008

Hi Ceki,

Thanks for your response. I have tested it with Tomcat 5.5.17.

-----Original Message-----
From: user-bounces at slf4j.org [mailto:user-bounces at slf4j.org] On Behalf Of Ceki Gulcu
Sent: Tuesday, September 23, 2008 3:48 PM
To: User list for the slf4j project
Subject: Re: [slf4j-user] jcl104-over-slf4j on the web's classpath causes redirection of tomcat's internal logging

Hello Zoltan,

I would not have expected Tomcat's logs to be intercepted by slf4j. Which version of Tomcat is this?

Szel, Zoltan (IT) wrote:
> Hi everyone,
> i have a web application which uses jcl as it's dependency(e.g spring).
> When i deploy my application on tomcat i notice, that tomcat's
> internal logging ends up in my config file. Is there a way to
> completely separate the internal logging from my applications logging?
> I know this can be filtered out very easily, but in that case i will
> still get logging output until my backend is configured via a servlet.
> I have googled a lot and haven't found any related issue, so i am
> wondering what i am doing wrong.
> Here is my classpath configuration:
> Tomcat's classpath:
>     commons-logging-api.jar
>     commons-logging.jar
>     log4j.jar
> Web apps classpath;
>     slf4j-api.jar
>     jcl104-over-slf4j.jar
>     logback jars
> I am using slf4j 1.4.3
> Any help appreciated.
> Thank you in advance!
> Regards
> Zoltan Szel

Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
user mailing list
user at slf4j.org

NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.

More information about the slf4j-user mailing list