[ https://issues.apache.org/jira/browse/LOG4J2-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242342#comment-16242342 ]
Ralph Goers commented on LOG4J2-2104: ------------------------------------- The problem you are mentioning is fixed in trunk as a result of LOG4J2-2055. Using Provider.class.getClassLoader will only return the ClassLoader for the log4j-api jar, which isn't what is desired. However, I am going to assign this to myself to remind me to look at the ServiceLoader code so I can understand why it is throwing the ServiceConfigurationError. > LoaderUtil getClassLoaders() method and while loops > --------------------------------------------------- > > Key: LOG4J2-2104 > URL: https://issues.apache.org/jira/browse/LOG4J2-2104 > Project: Log4j 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.9.1 > Reporter: Andrejus Chaliapinas > Assignee: Ralph Goers > Priority: Minor > > For v2.9.1 inside org.apache.logging.log4j.util.LoaderUtil and > getClassLoaders() method we have lines 120-123 as such: > ClassLoader parent = tcl; > while (parent != null && !classLoaders.contains(parent)) { > classLoaders.add(parent); > } > where it looks like some getParent() call is either missing or otherwise > "while" loop is not needed. > In line 111 tcl classloader already added into list of clasloaders: > classLoaders.add(tcl); > Was it an attempt to add all classloaders hierarchy or just some immediate > parents? -- This message was sent by Atlassian JIRA (v6.4.14#64029)