On Tue, 2003-09-30 at 06:05, Shapira, Yoav wrote:
> Howdy,
> One minor question: isn't the example CountingPatternConverter using StringBuffer in
> a way that causes the bad memory leak documented in Bug Parade 4724129?
> (http://developer.java.sun.com/developer/bugParade/bugs/4724129.html)
>
H
On Mon, 2003-09-29 at 22:47, Shapira, Yoav wrote:
> Howdy,
> I propose that log4j 1.3 (in its full distribution if there's more than
> one distribution) remove the statement that the performance classes are
> intended for internal uses only, and include the
> org.apache.log4j.performance classes in
Howdy,
One minor question: isn't the example CountingPatternConverter using StringBuffer in a
way that causes the bad memory leak documented in Bug Parade 4724129?
(http://developer.java.sun.com/developer/bugParade/bugs/4724129.html)
If so, we should add a little note in the code telling users
Here are some preliminary docs on PatternLayout version 1.3.
https://www.qos.ch/logging/PatternLayout.html
--
Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
import org.apache.Facetime;
Apache
Howdy,
I propose that log4j 1.3 (in its full distribution if there's more than
one distribution) remove the statement that the performance classes are
intended for internal uses only, and include the
org.apache.log4j.performance classes in the distribution jar. This will
help others independently