tag 8ecb73e317d4b106115b07e3dd03f02c2a8dd2f4
tagger David Pursehouse <david.pursehouse@sonymobile.com> Fri Apr 10 15:39:25 2015 +0900
object ae055c09e13b95278a795b4f5eb45dbe8b99a140

v2.10.2

commit ae055c09e13b95278a795b4f5eb45dbe8b99a140
author Luca Milanesio <luca.milanesio@gmail.com> Mon Mar 09 11:00:54 2015 +0000
committer Luca Milanesio <luca.milanesio@gmail.com> Mon Mar 09 11:08:20 2015 +0000
tree fd43bbd903ef126bca19f14fdd5b94db3ddabd74
parent 50e3b57294f445a51252c6d858aaf402ea3a24c7

Fix replication_log with external log4j.configuration

When using an external log4j configuration using the JVM container
option -Dlog4j.configuration=file:///... the replication log appender
wasn’t configured at all.

This was mainly due to the fact that all appenders were closed and 
removed before invoking the SystemLog.createAsyncAppender() that was
then unable to find any appender to attach.

Flipping the operations and using the single removeAppender instead
of the removeAllAppenders (the name is a lie: it does not only remove
but also *CLOSE* all the appenders, making them unusable) everything
is OK with an external configuration.

Issue: 3230
Change-Id: I4d9b153d49731a0a7d5c5df863c69dd2165cc883