[slf4j-dev] [JIRA] (SLF4J-351) Request for documentation improvements for SLF4JBridgeHandler and jul-to-slf4j usage.

[Oleksandr Gavenko (JIRA)]

Title: Message Title

Oleksandr Gavenko created an issue   SLF4J / SLF4J-351 Request for documentation improvements for SLF4JBridgeHandler and jul-to-slf4j usage. Issue Type: Improvement Affects Versions: 1.7.13 Assignee: SLF4J developers list Components: jul-to-slf4j Created: 02/Jan/16 9:26 PM Environment: any Priority: Major Reporter: Oleksandr Gavenko Originally I ask at http://stackoverflow.com/questions/34475776/what-is-impact-of-using-jul-to-slf4j-several-times-in-java-ee-spring-container Question about implication of calling SLF4JBridgeHandler.install() in container environment. I think that SLF4J may steal log messages from other webapp and redirect them to individual log file. Another concern is memory leaks when application is redeployed in container. I have dug in sources code: public class SLF4JBridgeHandler extends Handler { public static void install() { LogManager.getLogManager().getLogger("").addHandler(new SLF4JBridgeHandler()); } public static void uninstall() throws SecurityException { java.util.logging.Logger rootLogger = getRootLogger(); Handler[] handlers = rootLogger.getHandlers(); for (int i = 0; i < handlers.length; i++) { if (handlers[i] instanceof SLF4JBridgeHandler) { rootLogger.removeHandler(handlers[i]); } } } } I am not an expert of JUL but I guess that LogManager.getLogManager().getLogger("").addHandler(...) make global registration and affect all application used in single container. Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

_______________________________________________
slf4j-dev mailing list
slf4j-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-dev