Re: Disabling Garbage-free not working

Very glad to hear that. Thanks! The plan is to start the 2.6.2 release procedure very soon. On Tue, Jul 5, 2016 at 9:38 PM, Enric Jaen wrote: > I tried the 2.6.2 snapshot and it works Thanks > > El Lunes 4 de julio de 2016 9:47, Remko Popma > escribió: > > > The fix for https://issues.apac

Re: Disabling Garbage-free not working

I tried the 2.6.2 snapshot and it works Thanks El Lunes 4 de julio de 2016 9:47, Remko Popma escribió: The fix for https://issues.apache.org/jira/browse/LOG4J2-1434 checks that any large message increased the buffer size beyond the maximum. If it did then the buffer is trimmed to the

Re: Disabling Garbage-free not working

The fix for https://issues.apache.org/jira/browse/LOG4J2-1434 checks that any large message increased the buffer size beyond the maximum. If it did then the buffer is trimmed to the max size, so any large char[] arrays can be garbage collected. Before the fix the reusable buffer could grow indef

Re: Disabling Garbage-free not working

Many thanks for the response, I will give a try from the git. What does the fix do? Do I need to use any flag? When is 2.6.2 planned to be released? Thanks also for the Async appender workaround Enric El Domingo 3 de julio de 2016 7:25, Anthony Maire escribió: Another possible way to i

Re: Disabling Garbage-free not working

Another possible way to investigate is to wrap your RollingFile appender in an Async appender. Since there is only one thread that outputs, if it is a thread local related issue, it should disappear (and it may be use as a workaround until the next release) 2016-07-02 16:10 GMT+02:00 Remko Popma :

Re: Disabling Garbage-free not working

This issue may already have been fixed (see https://issues.apache.org/jira/browse/LOG4J2-1434 ). The fix will be in the upcoming 2.6.2 release. Can you verify if the problem still occurs with the current Log4j code in git master? Instructions on how to check out the latest source are here

Re: Disabling Garbage-free not working

Sorry typo again, was 3GB (not 3MB)  the total consumed memory by several char[]. For example I reveived a 60MB utf8 json and I see it resides inside a 250MB char[]  I have attached a dump screenshot Not sure if is relevant but I use RollingFile  :               I will try to reproduc

Re: Disabling Garbage-free not working

That's the bug I was trying to find. It sounds related. On 1 July 2016 at 23:09, Ralph Goers wrote: > Could this be the same issue as LOG4J2-1434? > > Ralph > > > On Jul 1, 2016, at 6:10 PM, Remko Popma wrote: > > > > Yes, Java 7 or higher, so Java 8 is fine. > > > > I'm still trying to underst

Re: Disabling Garbage-free not working

Could this be the same issue as LOG4J2-1434? Ralph > On Jul 1, 2016, at 6:10 PM, Remko Popma wrote: > > Yes, Java 7 or higher, so Java 8 is fine. > > I'm still trying to understand the problem. I understand that the application > receives and logs large JSON Strings. > After that I don't un

Re: Disabling Garbage-free not working

Yes, Java 7 or higher, so Java 8 is fine. I'm still trying to understand the problem. I understand that the application receives and logs large JSON Strings. After that I don't understand. Are these strings 3MB long, and they cause Log4j to build up 250MB buffers? Do you have a small program

Re: Disabling Garbage-free not working

typo sorry, log4j-core-2.6.1.jar El Viernes 1 de julio de 2016 22:08, Ralph Goers escribió: Did you really mean log4j 1.6 or was that a typo? Ralph > On Jul 1, 2016, at 8:38 AM, Enric Jaen wrote: > > Hello, > In our tomcat application we have a memory problem with logs kept in heap

Re: Disabling Garbage-free not working

Did you really mean log4j 1.6 or was that a typo? Ralph > On Jul 1, 2016, at 8:38 AM, Enric Jaen wrote: > > Hello, > In our tomcat application we have a memory problem with logs kept in heap.I > tried using log4j 1.6 and log4j2.enable.threadlocals = false but without > effect, what can be th

Re: Disabling Garbage-free not working

We use Java8 , is that ok?The problem is that we receive large json responses and log4j is creating char[]'s of 250MB up a total of 3MB and we  are suffering of continuos full gc. By releasing that mem we would go fine.Enric El Viernes 1 de julio de 2016 16:50, Remko Popma escribió:

Re: Disabling Garbage-free not working

Log4j 2.6.1 needs Java 7. Please provide more details about the memory problem. Sent from my iPhone > On 2016/07/02, at 0:38, Enric Jaen wrote: > > Hello, > In our tomcat application we have a memory problem with logs kept in heap.I > tried using log4j 1.6 and log4j2.enable.threadlocals =

Disabling Garbage-free not working

Hello,  In our tomcat application we have a memory problem with logs kept in heap.I tried using log4j 1.6 and log4j2.enable.threadlocals = false but without effect, what can be the reason? RegardsEnric