tree fd43bbd903ef126bca19f14fdd5b94db3ddabd74
parent 50e3b57294f445a51252c6d858aaf402ea3a24c7
author Luca Milanesio <luca.milanesio@gmail.com> 1425898854 +0000
committer Luca Milanesio <luca.milanesio@gmail.com> 1425899300 +0000

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