Re: Unexpected concurrent LoggerContext initialization

2021-11-15 Thread Volkan Yazıcı
I have created LOG4J2-3188 for this issue. On Fri, Nov 12, 2021 at 2:46 PM Volkan Yazıcı wrote: > *[Note that the shared `ParallelRunTest` is a self-sufficient code, that > is, one can simply copy-paste it into a Log4j test and run it.]* > > Wh

Re: Unexpected concurrent LoggerContext initialization

2021-11-12 Thread Volkan Yazıcı
*[Note that the shared `ParallelRunTest` is a self-sufficient code, that is, one can simply copy-paste it into a Log4j test and run it.]* When `ExecutionMode.SAME_THREAD` is used, everything works as expected: wc -l /tmp/ParallelRunTest-* 1000 /tmp/ParallelRunTest-A.log 1000 /tmp/ParallelRu

Re: Unexpected concurrent LoggerContext initialization

2021-11-11 Thread Remko Popma
What do the generated files look like? Is the output that is generated in concurrent mode longer or shorter than the expected length? Also, does it contain one entry (one log message) per line, or is it scrambled? Are entries ordered by time? On Fri, Nov 12, 2021 at 12:34 AM Ralph Goers wrote: >

Re: Unexpected concurrent LoggerContext initialization

2021-11-11 Thread Ralph Goers
How does it fail? Ralph > On Nov 11, 2021, at 1:42 AM, Volkan Yazıcı wrote: > > They sort of do exist, see JsonTemplateLayoutConcurrentEncodeTest >

Re: Unexpected concurrent LoggerContext initialization

2021-11-11 Thread Volkan Yazıcı
They sort of do exist, see JsonTemplateLayoutConcurrentEncodeTest . But I can add a dedicated test too.

Re: Unexpected concurrent LoggerContext initialization

2021-11-10 Thread Gary Gregory
Should this test be added to the repo with a TODO comment? Gary On Mon, Nov 8, 2021, 07:09 Volkan Yazıcı wrote: > Hello! Does anybody have an idea why the following test fails for > CONCURRENT execution mode, whereas it works for SAME_THREAD? > > import org.apache.logging.log4j.Level; > import

Unexpected concurrent LoggerContext initialization

2021-11-08 Thread Volkan Yazıcı
Hello! Does anybody have an idea why the following test fails for CONCURRENT execution mode, whereas it works for SAME_THREAD? import org.apache.logging.log4j.Level; import org.apache.logging.log4j.Logger; import org.apache.logging.log4j.core.LoggerContext; import org.apache.logging.log4j.core.con