Log4j 2 does not lock when calling appenders so you will not have the deadlock
you show.
Ralph
> On Jan 17, 2018, at 4:28 AM, Vikas Mangla wrote:
>
>
>
> Just to update, the kind of deadlocks we observe in the application as
> attached.
>
>
>
> From: Vikas Mangla
> Sent: Wednesda
From: Vikas Mangla
Sent: Wednesday, January 17, 2018 4:55 PM
To: 'log4j-...@logging.apache.org'
Subject: Moving from Log4j 1.2 to Log4j 2.0 to handle
concurrency/deadlocks/blocked threads issues.
Hi Team,
The request here is to understand if moving from Log4j 1.2 to Log4j 2.0 version
handles
Just to update, the kind of deadlocks we observe in the application as attached.
From: Vikas Mangla
Sent: Wednesday, January 17, 2018 4:55 PM
To: 'log4j-...@logging.apache.org'
mailto:log4j-...@logging.apache.org>>
Subject: Moving from Log4j 1.2 to Log4j 2.0 to handle
concurrency/deadlocks/b
Well, that's a decision we have to make. So far, logging-log4j-plugins
has not been released yet, so we are now free do decide how to do it.
I guess that logging-log4j-plugins over time will contain a diverse set
of appenders, layouts and other plugins for Log4j 2, each one in its own
Maven mo