Re: [Chainsaw] Removal of Log4j1

I've finished removing log4j1 from Chainsaw. If anybody would like to take a look, it is in a PR here: https://github.com/apache/logging-chainsaw/pull/11 The next steps probably are: * Make sure dependencies are up to date * Create a better way of documenting how receivers work other than just th

Re: Release 2.17.2

Here is another know broken feature in the 1.2 bridge, the getAllAppenders() API often (always?) returns an empty Enumeration. The guts of the class that implements the API is probably completely wrong in the context of a bridge, it should probably find all the appended wrappers and return those in

Re: Release 2.17.2

Hi, On Mon, Feb 21, 2022 at 3:01 PM Gary Gregory wrote: > > Note that I recently added DOMTestCase to the 1.2 bridge from the 1.2.17 > code base; this contains disabled tests for some non-trivial > configurations. I would appreciate extra eyes to debug these. I can look into the CategoryFactory

Re: log4net - performance hit because UserName is fetched always

Hi Denis Thanks for the report (: I'm happy to review contributions, though for this particular issue, it seems like the resolution is to cache the resolved user name, rather than allowing specifying the name via config. The whole point of this property is to log the username under which the pr

log4net - performance hit because UserName is fetched always

Hi all, we have upgraded the log4net version from 1.2.10 to the newest version 2.0.14 and are now facing performace issues. I already have done some investigation looking at the log4net code. With the ticket LOG4NET-205 a change has been introd

Re: Release 2.17.2

Note that I recently added DOMTestCase to the 1.2 bridge from the 1.2.17 code base; this contains disabled tests for some non-trivial configurations. I would appreciate extra eyes to debug these. Gary On Fri, Feb 18, 2022, 07:00 Gary Gregory wrote: > I took a brief look earlier this week, it's