rrent context, if logging
event itself will be used in appenders later / in another thread etc when
context is actually lost, and no way to restore those params, so they to be
retrieved in advance
Thanks,
Vladimir
On Tue, 22 Feb 2022 at 17:32, Denis Petker
mailto:denis.pet...@rohde-schwarz.com&
imir
On Tue, 22 Feb 2022 at 14:26, Dominik Psenner wrote:
> I believe the caching has already been implemented but don't have any
> references to mention right now.
>
> On Tue, 22 Feb 2022 at 09:56, Denis Petker
> >
> wrote:
>
> > Hi Davyd
> >
> > Thank
Hi Davyd,
your patch looks good to me. It resolves my issue.
Would be great if it could go into the next release.
Many thanks,
Denis
--
Denis Petker
Next Generation Solutions | 8BM3
Rohde & Schwarz GmbH & Co. KG
Hanomaghof 1 | 30449 Hanover
Phone: +49 511 678 07 146 | Fax: +49 511 67
rsuing
that with respect to another reported issue, but I could let that issue go for
now for a hastier release.
-d
On Feb 21 2022, at 7:22 pm, Denis Petker wrote:
>
> Hi all,
>
> we have upgraded the log4net version from 1.2.10 to the newest version 2.0.14
> and are now faci
s is the historic change causing the problem.
[cid:image001.png@01D8274E.AA9B33A0]
--
Denis Petker
Next Generation Solutions | 8BM3
Rohde & Schwarz GmbH & Co. KG
Hanomaghof 1 | 30449 Hanover
Phone: +49 511 678 07 146 | Fax: +49 511 678 07 200
Internet: www.ro
