, do
share.
Thanks,
Srijith.
-Original Message-
From: Ralph Goers
Sent: 26 February 2020 09:01
To: dev@logging.apache.org
Cc: Logging General ; Log4J Users List
; Sri Darshan Sreedharan
Subject: Re: Memory leak with log4j 2.13
Caution: This email originated from outside the organiza
Attachments generally do not make it to the mailing lists. There is no leak
report attached to the email.
I think you are going to have to explain a little more as to what your
application was doing that would cause so many Console Appenders. While there
is a Default Configuration there is no
Hi Srijith,
Thanks for reaching out. Could you file a jira issue to track all of this
information? If you could attach or link a minimal reproducer that would be
tremendously helpful.
Thanks,
-ck
On Wed, Feb 26, 2020, at 07:25, Srijith Kochunni wrote:
> Hi All,
>
> We recently upgraded our
Hi All,
We recently upgraded our application to log4j 2.13 from log4j
1.2.15. Since the upgrade, we've noticed in one of our test setups that the
application is running out of heap space. Upon inspecting the heap dump, we
found that there are almost a 100 thousand entries in the Ha
