Re: Pax Logging loses track of loggers because of change made when you added generics in December 2015

Hello again ;) Thanks for detailed check! I confess - I wasn't able to do `git apply < xxx.patch`, so I did it manually and: - I forgot about changing the clear() to removal of "bundle.*" entries - I didn't notice double put() This time I did 2nd review and here's the result:

Re: Pax Logging loses track of loggers because of change made when you added generics in December 2015

Hi. I very much appreciate the update and the new release. Thank you. I'm glad that the memory leak patch helped and that you could see from your updated tests what I had seen regarding leaks. *I hate to tell you this, but you'll need to make some fixes and release 1.10.x again.* *First*, you

Re: Pax Logging loses track of loggers because of change made when you added generics in December 2015

Good, thanks for the update. Regards JB On Mon, May 4, 2020 at 10:43 AM Grzegorz Grzybek wrote: > Hello > > Nope, it's not. Though I've enhanced the memory-related tests. And I'll > prepare new 1.11.x/2.0.x releases too, because of > https://ops4j1.jira.com/browse/PAXLOGGING-312 == >

Re: Pax Logging loses track of loggers because of change made when you added generics in December 2015

Hello Nope, it's not. Though I've enhanced the memory-related tests. And I'll prepare new 1.11.x/2.0.x releases too, because of https://ops4j1.jira.com/browse/PAXLOGGING-312 == https://issues.apache.org/jira/browse/LOG4J2-2819 == CVE-2020-9488 soon. regards Grzegorz Grzybek pon., 4 maj 2020 o

Re: Pax Logging loses track of loggers because of change made when you added generics in December 2015

Hi Grzegorz, Pax Logging 1.11.x is not impacted ? Regards JB On Mon, May 4, 2020 at 10:40 AM Grzegorz Grzybek wrote: > Hello again > > Without waiting, I've just released pax-logging 1.10.6 version - I hope > it'll solve all your (Monica Ron) problems ;) > > regards > Grzegorz Grzybek > >

Re: Pax Logging loses track of loggers because of change made when you added generics in December 2015

Hello again Without waiting, I've just released pax-logging 1.10.6 version - I hope it'll solve all your (Monica Ron) problems ;) regards Grzegorz Grzybek pon., 4 maj 2020 o 09:10 Grzegorz Grzybek napisał(a): > Hello³ > > And finally - many many thanks for your patch! I'm grateful because

Re: Jira or github?

On Monday, April 27, 2020 9:15:16 AM CEST 'Achim Nierbeck' via OPS4J wrote: > Hi, > > in the past we needed to do a "lock-down" on self-registration for the Jira > Instance due to tremendous amount of spam in Jira Issues and on the > confluence pages. > This increases the burden for people to

Re: Pax Logging loses track of loggers because of change made when you added generics in December 2015

Hello³ And finally - many many thanks for your patch! I'm grateful because after applying your patch without changes, my Memory tests (extended to cover all remaining logging APIs/facades) pass without memory leaks on -Xmx64m. The change is:

Re: Pax Logging loses track of loggers because of change made when you added generics in December 2015

Hello² In Pax Logging 1.10.x it's not that good. - org.ops4j.pax.logging.log4jv2.Log4jv2Logger - 10001 instances - ok - org.ops4j.pax.logging.log4j2.internal.PaxLoggerImpl - 10010 instances - ok - org.apache.logging.log4j.core.Logger - 10010 instances - ok -

Re: Pax Logging loses track of loggers because of change made when you added generics in December 2015

Hello FYI, I've changed the memory tests to do logging via 7 "frontends" for each of 3 "backends". These frontends are: org.slf4j.Logger slf4jLogger = org.slf4j.LoggerFactory.getLogger(name); slf4jLogger.trace("TRACE through SLF4J"); org.apache.commons.logging.Log commonsLogger =