Hi Remko/Matt,
Yes the AsyncLogger.ThreadNameStrategy=UNCACHED solved it.
Thank you
On 2017-02-15 23:21 (-0500), Remko Popma wrote:
> Hi Leon,
>
> Yes by default the thread name is cached.
> There is a system property to switch that off: see
> https://github.com/apache/logging-log4j2/blob/
The usual reason for using char[] instead of String is so you can overwrite
it in heap without having to wait for garbage collection and is only used
for security reasons (e.g., a password). I'm going to guess legacy reasons
for the char[], but native code could make sense, too.
On 15 February 201
Hi Leon,
Yes by default the thread name is cached.
There is a system property to switch that off: see
https://github.com/apache/logging-log4j2/blob/master/log4j-core/src/main/java/org/apache/logging/log4j/core/async/ThreadNameCachingStrategy.java
The reason for the caching is that every call to
Only thing I can think of offhand is an issue with ReusableLogEventFactory.
I don't see anything in the 2.8 changelog fixing anything related. Could
you try disabling GC-free mode? <
https://logging.apache.org/log4j/2.x/manual/garbagefree.html>
I'm sure Remko will have some ideas when he's online.
