https://issues.apache.org/bugzilla/show_bug.cgi?id=50614
--- Comment #6 from Amr ElAdawy <amr.elad...@etisalat.com> --- (In reply to siva from comment #5) > Thanks for your quick reply > > In my case, since I have a lot of configuration files, i have to manually > disable the consoleAppender(using the command mentioned) for every config > file. Is there any other workaround in the above scenario?. > > I have the following questions > > 1. Is disabling the consoleAppender the only possible fix for the above > issue in 1.2.x. Can you please specify if there are other alternatives?. > > 2. Does the patch for bug - 50213 defect resolve the consoleAppender issue ? > > 3. I understand from comment 6(given by Ralph Goers) in Defect Id: 51047 > that this issue was fixed in Log4j 2.0. Ralph also talks about an adapter > for > the 1.2 API. Could you please provide a reference to the same?. > > Appreciate your feedback at the earliest. Hi, the idea behind disabling console Appender is to reduce the IO operations which are causing the lock issue (as per my understanding). Regarding Log4J 2.0 I have no idea as I moved to LogBack and I stopped using Log4J anymore. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
