logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Brennan <Michael_Bren...@Allegis.com>
Subject RE: Memory footprint question re large-scale J2EE deployment
Date Thu, 05 Apr 2001 00:39:32 GMT
Yes, they are just references to hash table entries. Once a Category object
for a particular logging category is instantiated, Category.getInstance will
always return a reference to the already instantiated instance.

The static member approach is a good pattern, IMO. That's what I do. I also
typically use one Category per package, although occassionally will use more
(and may even have more than one Category for a particular class if I want
to be able to filter logging output on a more granular level).

> -----Original Message-----
> From: Johnson, Clay [mailto:clay.johnson@vignette.com]
> Sent: Wednesday, April 04, 2001 4:18 PM
> To: 'LOG4J Users Mailing List'
> Subject: RE: Memory footprint question re large-scale J2EE deployment
> Is this really an issue?  I thought category instances were simply
> references (pointers) to the hierarchy hash table entry.  And 
> if you use
> static categories, for that matter, you have only one per class.
> Static members also minimize hash lookup.

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

View raw message