commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Westbom <>
Subject Re: beanutils, too much logging
Date Thu, 10 Apr 2003 20:08:35 GMT
If this is in your servlet layer Tomcat will load from the application
classloader first before deferring.

--- Darrel Riekhof <> wrote:
> I'm running a struts 1.1 application on jboss 3.0.6 / tomcat 4.1.18.  We're
> using BeanUtils to automatically go back and forth between struts forms and
> middleware view classes.  Everytime I do this, beanutils spits out a ton of
> messages to the jboss server console that look like this:
> 12:37:56, 115 INFO  [STDOUT] 1557513 [Thread-9] DEBUG
> org.apache.commons.beanutils.BeanUtils  -   setProperty(foo1=bar1
> foo2=bar2
> foo3=bar3
> <etc>)
> JBoss is using log4j.  I'm pretty sure it picks up its settings from JBoss's
> server/default/conf/log4j.xml, and that I wouldn't be able to define my own
> webapps or xml file because JBoss will load this one first.
> So, I could either change JBoss's log4j.xml or do runtime configuration
> using the log4j configurator api.  Assuming this is correct, how would I
> configure it to filter out all the beanutil logging and still keep getting
> all the other messages?
> Also, in the sample log entry above, why does it say that its INFO level and
> DEBUG level?  Are beanutil log messages getting nested inside jboss's?
> thx, Darrel
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more

View raw message