;ll be sticking
with the 1.2.x branch for the foreseeable future.
From: Gary Gregory
To: Log4J Users List ; Dave Glasser
Sent: Thursday, December 17, 2015 6:32 PM
Subject: Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap
Can you list which bugs in JIRA you
around it some other way.
From: Gary Gregory
To: Dave Glasser ; Log4J Users List
Sent: Thursday, December 17, 2015 3:16 PM
Subject: Re: still: Memoryleak - org.apache.log4j.helpers.ThreadLocalMap
Hello,
Log4j 1 has reached EOL. For Java 6 support you can use 2.3.
Gary
On Dec 1
To any Log4j devs on the list, if Veit has found a bug in 1.2.17, please,
please, fix it and release 1.2.18. I cannot use 2.5 because my code has to run
under Java 1.6. I suspect that is the case with a lot of developers who deploy
on WebSphere or WebLogic.
From: Veit Guna
To: log4j
using 1.2.x, and it can't be taken
out.
I notice that with the patch the size is updated through the
RollingFileManager, but I can't figure out a way to get a reference to that.
Any help on that one?
From: Ralph Goers
To: Log4J Users List ; Dave Glasser
Sent: Wednesday, Decemb
I'm using Log4j 2.3, rather than the latest 2.x version, because my code needs
to run on Java 1.6. Anyway, I am configuring everything programmatically. When
I create the RollingFileAppender with RollingFileAppender.createAppender, I
pass in as the policy parameter:
SizeBasedTriggeringPolicy.
