GitHub user paladox edited a comment on the discussion: Help with migrating
from log4j to log4j2 (we also use a slf4j -> log4j)
I found another alternative:
```
LoggerContext ctx = (LoggerContext) LogManager.getContext(false);
ctx.addPropertyChangeListener(
evt -> {
if ("config".equals(evt.getPropertyName())) {
synchronized (lock) {
if (async == null || !async.isStarted()) {
enableLogging();
}
}
}
});
```
Seems the problem happens to all classes that use AsyncAppender or anything
really and when you call reconfigure it stops it for all. So the above changes
would have to happen in all the classes. But is there an alternative? Am I
doing things wrong?
Seems there's an issue with reconfigure and when you do things programatically.
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3914#discussioncomment-14331488
----
This is an automatically sent email for dev@logging.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
