SLF4J / SLF4J-568 [Open] Fix ServiceLoader usage in servlet environment ============================== Here's what changed in this issue in the last few minutes. This issue has been created View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-568 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 28/Sep/22 2:07 PM Summary: Fix ServiceLoader usage in servlet environment Issue Type: Improvement Assignee: Ceki Gülcü Created: 28/Sep/22 2:07 PM Priority: Major Reporter: Ceki Gülcü External issue ID: https://github.com/qos-ch/slf4j/pull/304 Description: If both the servlet container and a web application use SLF4J, {{ServiceLoader}} calls are susceptible to three problems: # The SLF4J copy in the webapp detects the common providers by can not instantiate them (they implement a different copy of {{SLF4JProviderService}}), # The SLF4J copy in the common classloader can bind the providers in the webapp classloader and cause a memory leak, # If the server uses a SecurityManager the static initialization of {{LoggerFactory}} fails if called by unprivileged code. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)