The Apache Log4j 2 team is pleased to announce the Log4j 2.12.0 release!
Apache Log4j is a well known framework for logging application behavior. Log4j
2 is an upgrade to Log4j that provides significant improvements over its
predecessor, Log4j 1.x, and provides many other modern features such as
Even better! Thanks.
On Sat, Jun 29, 2019 at 11:47, Ralph Goers
wrote:
> Umm. The release went live last night so there can’t be more release
> candidates.
>
> Ralph
>
> > On Jun 29, 2019, at 9:31 AM, Matt Sicker wrote:
> >
> > I can update it, yes, but I don’t think it’s warrant for another re
The last commit was on 2017 so, its becoming a less favor to new startup
projects. I tried to contribute by adding latest .net framework support so,
at least need a PR review support to get this on track.
Thanks for understanding.
Regards,
Kabilan
On Sat, 29 Jun, 2019, 4:31 AM Jochen Wiedmann,
w
Umm. The release went live last night so there can’t be more release candidates.
Ralph
> On Jun 29, 2019, at 9:31 AM, Matt Sicker wrote:
>
> I can update it, yes, but I don’t think it’s warrant for another release
> candidate.
>
> On Sat, Jun 29, 2019 at 10:31, Gary Gregory wrote:
>
>> On Fr
If you’re making loggers per user, for example, that might make more sense
as thread context data.
On Sat, Jun 29, 2019 at 06:11, Dominik Psenner wrote:
> Creating this many appenders is troublesome also for any operating system
> because the number of open (file) handles is limited. A little bi
I can update it, yes, but I don’t think it’s warrant for another release
candidate.
On Sat, Jun 29, 2019 at 10:31, Gary Gregory wrote:
> On Fri, Jun 28, 2019 at 11:32 AM Matt Sicker wrote:
>
> > Ok, I see that it's already tested right there. Then it really is safe
> > to add an assumeThat() to
On Fri, Jun 28, 2019 at 11:32 AM Matt Sicker wrote:
> Ok, I see that it's already tested right there. Then it really is safe
> to add an assumeThat() to the test that uses reflection to access the
> deprecated API. That test can be safely ignored once the deprecated
> API is removed since we alre
On Sat, Jun 29, 2019 at 1:21 PM Dominik Psenner wrote:
> We could also push log4net back to incubation. What do you think?
If availability of people is an issue, then this would be an excellent
way of exhausting those even more.
Jochen
Hey,
Thanks Matt for providing feedback on the project. I am better at the
moment but still have hard limits in place regarding the time I spend in
front of computers because it does me good.
Given the limited resources I am donating to the project there won't be
noticable progress in the foresee
Creating this many appenders is troublesome also for any operating system
because the number of open (file) handles is limited. A little bit old anf
thus possibly outdated but still provides insights into windows specific
details and highlights some corner stones for orientation:
https://blogs.tec
You are creating millions of loggers? Meaning either of
- I have a million different logger Id's, and create a logger for
every single one, or
- I have a limited number of different logger Id's, but invoke
LoggerContext.getLogger(String), or
LogManager.getLogger(String), or something similar, wi
11 matches
Mail list logo
