[
https://issues.apache.org/jira/browse/LOG4J2-2754?focusedWorklogId=365103&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-365103
]
ASF GitHub Bot logged work on LOG4J2-2754:
------------------------------------------
Author: ASF GitHub Bot
Created on: 31/Dec/19 23:27
Start Date: 31/Dec/19 23:27
Worklog Time Spent: 10m
Work Description: carterkozak commented on issue #328: LOG4J2-2754:
LoaderUtil.getClassLoaders may discover additional loaders
URL: https://github.com/apache/logging-log4j2/pull/328#issuecomment-570004977
Thanks Ralph, tests all pass, I've merged this commit. It's not a clean
cherry-pick to master because fbde9cd0ef was not applied to release-2.x.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 365103)
Time Spent: 50m (was: 40m)
> LoaderUtil.getClassLoaders fails to update loop state
> -----------------------------------------------------
>
> Key: LOG4J2-2754
> URL: https://issues.apache.org/jira/browse/LOG4J2-2754
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.13.0
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Same problem as LOG4J2-2104, but for final 'ClassLoader current =
> LoaderUtil.class.getClassLoader();'
> The while loop acts as a simple conditional (unless a classloader is defined
> with an incorrect 'equals' method, then it loops infinitely -- I've not seen
> this behavior in practice though).
> It appears that getThreadContextClassLoader can return a null ClassLoader,
> which ends up in the getClassLoaders result erroneously.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
