logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott M Stark" <Scott_St...@displayscape.com>
Subject Re: Memory footprint question re large-scale J2EE deployment
Date Wed, 04 Apr 2001 23:12:16 GMT
You don't have to follow the pattern of having a Category instance per
class. I use one Category per package and sometimes one Category
for a logical grouping of packages. 

----- Original Message ----- 
From: "L. Scott Emmons" <scotte@center.uscs.com>
To: <log4j-user@jakarta.apache.org>
Sent: Wednesday, April 04, 2001 3:11 PM
Subject: Memory footprint question re large-scale J2EE deployment

> Was curious if anyone has measured the memory footprint of log4j. Some
> of our architecture folks are worried that having 100's of classes (EJB,
> Servlet, etc) instantiating log4j objects will be a problem. We plan on
> using the JMSAppender, if that makes any significant difference.
> I'm curious how other folks have implemented log4j in large-scale
> projects. Do you instantiate log4j objects in each class?
> Thanks,
> -Scott

To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org

View raw message