SLF4J / SLF4J-548 [Open] Loading services (plugins) with the caller's ClassLoader
============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-548 ============================== 1 comment ------------------------------ Piotr P. Karwasz on 02/Sep/22 11:30 PM [~ceki], I also believe that calling {{ServiceLoader.load}} without a classloader parameter is a bug: if SLF4J is in the common classloader of a servlet container, it can unintentionally bind with a service provider in a webapp classloader. This will cause a memory leak whenever the application is undeployed (and a broken logging system). I submitted [PR #304|https://github.com/qos-ch/slf4j/pull/304] to solve this and two other {{ServiceLoader}} problems. It should also solve [~chadlwilson]'s problem, which manifests when a copy of SLF4J bundled with a webapp tries to load service providers in its parent classloader. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59) _______________________________________________ slf4j-dev mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/slf4j-dev
