[ https://issues.jboss.org/browse/LOGMGR-124?page=com.atlassian.jira.plugin... ] James Perkins commented on LOGMGR-124: -------------------------------------- Unfortunately this has not yet been looked at due to it's large impact. The log manager itself would require marker support. Then JBoss Logging would need to be updated to support it in a way which does not break compatibility. Our fork of log4j would need to be updated as well followed by the slf4j bridge. Again both of those would need to done in a way to not break backwards compatibility. As far as changing the log manager implementation in WildFly. It _may_ be possible, but I haven't tried it. You'd need to remove the logging subsystem. Then you'd need to edit the {{jboss-logmanager-*.jar}} and remove the {{META-INF/services/java.util.logging.LogManager}} service file. You'd then need to ensure that somehow the new log manager ends up visible. It would likely have to be on the boot class path would be my guess. If this works it would only work for standalone as well. Domain mode requires the JBoss Log Manager. -- This message was sent by Atlassian Jira (v7.13.8#713008)