You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Ben Souther <bs...@fwdco.com> on 2004/09/29 16:42:25 UTC
[OT] Re: log4j.properties file co-opting container logging.
Got it...
The app in question, uses Axis which uses commons-logging (CL).
The addition of the log4j config file must have co-opted the Axis src.
On Wed, 2004-09-29 at 09:25, Ben Souther wrote:
> Tomcat 5.0.28
> RH Linux 7.3/Windows 2000
>
> After adding log4j jar file to:
> <CONTEXT>/WEB-INF/lib
>
> and log4j.properties to:
> <CONTEXT>/WEB-INF/classes
>
> my application's log file (the one specified in log4j.properties)
> is being filled up with container generated debugging (sample below).
>
> It doesn't seem to happen when with a clean restart of Tomcat.
> The app was deployed as a war file with all the l4j files intact.
>
> I'm trying to reproduce in a sample app (with no luck so far) that I can
> post.
>
> In the mean time, has anyone seen anything like this before?
>
>
>
>
>
>
> ==========================sample========================
> DEBUG: Convert string '30' to class 'int'
> DEBUG: Using converter
> org.apache.commons.beanutils.converters.IntegerConverter@11d2572
> DEBUG: Registering Catalina:type=Manager,path=/appname,host=localhost
> DEBUG: Force random number initialization starting
> DEBUG: Opening /dev/urandom
> DEBUG: Getting message digest component for algorithm MD5
> DEBUG: Completed getting message digest component
> DEBUG: getDigest() 1
> DEBUG: Force random number initialization completed
> DEBUG: Start: Loading persisted sessions
> DEBUG: Loading persisted sessions from SESSIONS.ser
> DEBUG: Creating custom object input stream for class loader
> DEBUG: Loading 0 persisted sessions
> DEBUG: Finish: Loading persisted sessions
> DEBUG: Initializing the Web Service App.........
> DEBUG: ContextListener. rbo_account: swdev
> DEBUG: Creating ApplicationCodeLists Object
> DEBUG: RBO ACCOUNT: swdev
> DEBUG: *** Getting error Codes from RBO
> DEBUG: 0 valid sessions open.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: [OT] Re: log4j.properties file co-opting container logging.
Posted by Filip Hanik - Dev <de...@hanik.com>.
yes, in your log4j configuration file you can set up your logging categories, that way you can omit anything that comes from
org.apache.* classfiles
Filip
----- Original Message -----
From: "Ben Souther" <bs...@fwdco.com>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Wednesday, September 29, 2004 10:27 AM
Subject: Re: [OT] Re: log4j.properties file co-opting container logging.
Do you know what logger is used by default by commons-logging in Tomcat
if log4j isn't present?
And... Is there a way to configure it separately from log4j to separate
my logging from Axis's?
On Wed, 2004-09-29 at 11:22, Jacob Kjome wrote:
> Quoting Ben Souther <bs...@fwdco.com>:
>
> > Got it...
> >
> > The app in question, uses Axis which uses commons-logging (CL).
> > The addition of the log4j config file must have co-opted the Axis src.
> >
>
> Yep, just set the org.apache or org.apache.commons logger to warn or whatever
> level you prefer which will squelch all but the most important messages.
>
> Jake
>
> >
> > On Wed, 2004-09-29 at 09:25, Ben Souther wrote:
> > > Tomcat 5.0.28
> > > RH Linux 7.3/Windows 2000
> > >
> > > After adding log4j jar file to:
> > > <CONTEXT>/WEB-INF/lib
> > >
> > > and log4j.properties to:
> > > <CONTEXT>/WEB-INF/classes
> > >
> > > my application's log file (the one specified in log4j.properties)
> > > is being filled up with container generated debugging (sample below).
> > >
> > > It doesn't seem to happen when with a clean restart of Tomcat.
> > > The app was deployed as a war file with all the l4j files intact.
> > >
> > > I'm trying to reproduce in a sample app (with no luck so far) that I can
> > > post.
> > >
> > > In the mean time, has anyone seen anything like this before?
> > >
> > >
> > >
> > >
> > >
> > >
> > > ==========================sample========================
> > > DEBUG: Convert string '30' to class 'int'
> > > DEBUG: Using converter
> > > org.apache.commons.beanutils.converters.IntegerConverter@11d2572
> > > DEBUG: Registering Catalina:type=Manager,path=/appname,host=localhost
> > > DEBUG: Force random number initialization starting
> > > DEBUG: Opening /dev/urandom
> > > DEBUG: Getting message digest component for algorithm MD5
> > > DEBUG: Completed getting message digest component
> > > DEBUG: getDigest() 1
> > > DEBUG: Force random number initialization completed
> > > DEBUG: Start: Loading persisted sessions
> > > DEBUG: Loading persisted sessions from SESSIONS.ser
> > > DEBUG: Creating custom object input stream for class loader
> > > DEBUG: Loading 0 persisted sessions
> > > DEBUG: Finish: Loading persisted sessions
> > > DEBUG: Initializing the Web Service App.........
> > > DEBUG: ContextListener. rbo_account: swdev
> > > DEBUG: Creating ApplicationCodeLists Object
> > > DEBUG: RBO ACCOUNT: swdev
> > > DEBUG: *** Getting error Codes from RBO
> > > DEBUG: 0 valid sessions open.
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: [OT] Re: log4j.properties file co-opting container logging.
Posted by Jacob Kjome <ho...@visi.com>.
Quoting Ben Souther <bs...@fwdco.com>:
> Do you know what logger is used by default by commons-logging in Tomcat
> if log4j isn't present?
>
I'm not very privy to the internals of commons-logging, but I think they have
some sort of simple logger which is used when there is no other logging
implementation available. Don't quote me on that, though.
> And... Is there a way to configure it separately from log4j to separate
> my logging from Axis's?
>
Yes, you could log to a separate logger repository, but you'd have to use a
repository selector that is not so global like the ContextJNDISelector is. The
fact is, anything that uses log4j and uses the same logger repository will end
up being controlled by the configuration for that logger repository.
Ceki is working on something called logger domains, but I'm not entirely sure
what that entails. What I suggest is setting the root logger to some higher
level such as "warn" and then specifically setting less strict logger levels
for packages or classes in which you specifically want to see more information.
This should, effectively, control the cross-library aspect of the logger
repository.
Jake
>
>
>
> On Wed, 2004-09-29 at 11:22, Jacob Kjome wrote:
> > Quoting Ben Souther <bs...@fwdco.com>:
> >
> > > Got it...
> > >
> > > The app in question, uses Axis which uses commons-logging (CL).
> > > The addition of the log4j config file must have co-opted the Axis src.
> > >
> >
> > Yep, just set the org.apache or org.apache.commons logger to warn or
> whatever
> > level you prefer which will squelch all but the most important messages.
> >
> > Jake
> >
> > >
> > > On Wed, 2004-09-29 at 09:25, Ben Souther wrote:
> > > > Tomcat 5.0.28
> > > > RH Linux 7.3/Windows 2000
> > > >
> > > > After adding log4j jar file to:
> > > > <CONTEXT>/WEB-INF/lib
> > > >
> > > > and log4j.properties to:
> > > > <CONTEXT>/WEB-INF/classes
> > > >
> > > > my application's log file (the one specified in log4j.properties)
> > > > is being filled up with container generated debugging (sample below).
> > > >
> > > > It doesn't seem to happen when with a clean restart of Tomcat.
> > > > The app was deployed as a war file with all the l4j files intact.
> > > >
> > > > I'm trying to reproduce in a sample app (with no luck so far) that I
> can
> > > > post.
> > > >
> > > > In the mean time, has anyone seen anything like this before?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ==========================sample========================
> > > > DEBUG: Convert string '30' to class 'int'
> > > > DEBUG: Using converter
> > > > org.apache.commons.beanutils.converters.IntegerConverter@11d2572
> > > > DEBUG: Registering Catalina:type=Manager,path=/appname,host=localhost
> > > > DEBUG: Force random number initialization starting
> > > > DEBUG: Opening /dev/urandom
> > > > DEBUG: Getting message digest component for algorithm MD5
> > > > DEBUG: Completed getting message digest component
> > > > DEBUG: getDigest() 1
> > > > DEBUG: Force random number initialization completed
> > > > DEBUG: Start: Loading persisted sessions
> > > > DEBUG: Loading persisted sessions from SESSIONS.ser
> > > > DEBUG: Creating custom object input stream for class loader
> > > > DEBUG: Loading 0 persisted sessions
> > > > DEBUG: Finish: Loading persisted sessions
> > > > DEBUG: Initializing the Web Service App.........
> > > > DEBUG: ContextListener. rbo_account: swdev
> > > > DEBUG: Creating ApplicationCodeLists Object
> > > > DEBUG: RBO ACCOUNT: swdev
> > > > DEBUG: *** Getting error Codes from RBO
> > > > DEBUG: 0 valid sessions open.
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> > >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: [OT] Re: log4j.properties file co-opting container logging.
Posted by Ben Souther <bs...@fwdco.com>.
Do you know what logger is used by default by commons-logging in Tomcat
if log4j isn't present?
And... Is there a way to configure it separately from log4j to separate
my logging from Axis's?
On Wed, 2004-09-29 at 11:22, Jacob Kjome wrote:
> Quoting Ben Souther <bs...@fwdco.com>:
>
> > Got it...
> >
> > The app in question, uses Axis which uses commons-logging (CL).
> > The addition of the log4j config file must have co-opted the Axis src.
> >
>
> Yep, just set the org.apache or org.apache.commons logger to warn or whatever
> level you prefer which will squelch all but the most important messages.
>
> Jake
>
> >
> > On Wed, 2004-09-29 at 09:25, Ben Souther wrote:
> > > Tomcat 5.0.28
> > > RH Linux 7.3/Windows 2000
> > >
> > > After adding log4j jar file to:
> > > <CONTEXT>/WEB-INF/lib
> > >
> > > and log4j.properties to:
> > > <CONTEXT>/WEB-INF/classes
> > >
> > > my application's log file (the one specified in log4j.properties)
> > > is being filled up with container generated debugging (sample below).
> > >
> > > It doesn't seem to happen when with a clean restart of Tomcat.
> > > The app was deployed as a war file with all the l4j files intact.
> > >
> > > I'm trying to reproduce in a sample app (with no luck so far) that I can
> > > post.
> > >
> > > In the mean time, has anyone seen anything like this before?
> > >
> > >
> > >
> > >
> > >
> > >
> > > ==========================sample========================
> > > DEBUG: Convert string '30' to class 'int'
> > > DEBUG: Using converter
> > > org.apache.commons.beanutils.converters.IntegerConverter@11d2572
> > > DEBUG: Registering Catalina:type=Manager,path=/appname,host=localhost
> > > DEBUG: Force random number initialization starting
> > > DEBUG: Opening /dev/urandom
> > > DEBUG: Getting message digest component for algorithm MD5
> > > DEBUG: Completed getting message digest component
> > > DEBUG: getDigest() 1
> > > DEBUG: Force random number initialization completed
> > > DEBUG: Start: Loading persisted sessions
> > > DEBUG: Loading persisted sessions from SESSIONS.ser
> > > DEBUG: Creating custom object input stream for class loader
> > > DEBUG: Loading 0 persisted sessions
> > > DEBUG: Finish: Loading persisted sessions
> > > DEBUG: Initializing the Web Service App.........
> > > DEBUG: ContextListener. rbo_account: swdev
> > > DEBUG: Creating ApplicationCodeLists Object
> > > DEBUG: RBO ACCOUNT: swdev
> > > DEBUG: *** Getting error Codes from RBO
> > > DEBUG: 0 valid sessions open.
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: [OT] Re: log4j.properties file co-opting container logging.
Posted by Jacob Kjome <ho...@visi.com>.
Quoting Ben Souther <bs...@fwdco.com>:
> Got it...
>
> The app in question, uses Axis which uses commons-logging (CL).
> The addition of the log4j config file must have co-opted the Axis src.
>
Yep, just set the org.apache or org.apache.commons logger to warn or whatever
level you prefer which will squelch all but the most important messages.
Jake
>
> On Wed, 2004-09-29 at 09:25, Ben Souther wrote:
> > Tomcat 5.0.28
> > RH Linux 7.3/Windows 2000
> >
> > After adding log4j jar file to:
> > <CONTEXT>/WEB-INF/lib
> >
> > and log4j.properties to:
> > <CONTEXT>/WEB-INF/classes
> >
> > my application's log file (the one specified in log4j.properties)
> > is being filled up with container generated debugging (sample below).
> >
> > It doesn't seem to happen when with a clean restart of Tomcat.
> > The app was deployed as a war file with all the l4j files intact.
> >
> > I'm trying to reproduce in a sample app (with no luck so far) that I can
> > post.
> >
> > In the mean time, has anyone seen anything like this before?
> >
> >
> >
> >
> >
> >
> > ==========================sample========================
> > DEBUG: Convert string '30' to class 'int'
> > DEBUG: Using converter
> > org.apache.commons.beanutils.converters.IntegerConverter@11d2572
> > DEBUG: Registering Catalina:type=Manager,path=/appname,host=localhost
> > DEBUG: Force random number initialization starting
> > DEBUG: Opening /dev/urandom
> > DEBUG: Getting message digest component for algorithm MD5
> > DEBUG: Completed getting message digest component
> > DEBUG: getDigest() 1
> > DEBUG: Force random number initialization completed
> > DEBUG: Start: Loading persisted sessions
> > DEBUG: Loading persisted sessions from SESSIONS.ser
> > DEBUG: Creating custom object input stream for class loader
> > DEBUG: Loading 0 persisted sessions
> > DEBUG: Finish: Loading persisted sessions
> > DEBUG: Initializing the Web Service App.........
> > DEBUG: ContextListener. rbo_account: swdev
> > DEBUG: Creating ApplicationCodeLists Object
> > DEBUG: RBO ACCOUNT: swdev
> > DEBUG: *** Getting error Codes from RBO
> > DEBUG: 0 valid sessions open.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org