Hello again,
I have tested with the latest version of log4j2, 2.8.2 and it seems that
this is still happening.
Any ideea on how could i work around this? We have a release today and
apparently this bug is forcing us to revert to log4j1.
Thank you!
Bogdan
On Thu, Aug 10, 2017 at 8:42 PM, Bogdan
I will do this tomorrow. Thanks!
> On 10 Aug 2017, at 19:28, Gary Gregory <garydgreg...@gmail.com> wrote:
>
> Can you update to 2.8.2 so we can compare to the current codebase?
>
> Gary
>
>> On Aug 10, 2017 09:37, "Bogdan" <bgdnb...@gmail.com> w
