[logback-dev] why ayncAppender not use mutil threads to consume blocking queue in the logback v_1.3.0-alpha4
KnightWu
1239562508guge at gmail.com
Fri Jan 11 09:42:51 CET 2019
hello, the version is logback v_1.3.0-alpha4, maybe i dont understand all, so
i have a couple of stupid questions.
1. AsyncAppenderBase.java , line 57 , i only see a worker (a thread) to
consume blocking queue, is there any configuration to change to mutil
threads? Or , why not use mutil threads to consume, i think it may improve
performance .
2. OutputStreamAppender.java , line 217, judge whether started or not, but
this line is before the write lock . OutputStreamAppender.java , line 197,
is it possible that the outputstream is already closed , but some write
threads are still waiting for the write lock in line 297, then write to
stream that are already closed?
3. OutputStreamAppender , line 141, why not immediately flush the
outputstream after writing footer bytes?
thank to you , first. Can anyone give me answer?
--
Sent from: http://logback.10977.n7.nabble.com/Developer-f3683.html
More information about the logback-dev
mailing list