This discussion has moved to GitHub: https://github.com/apache/logging-log4j2/issues/4058
On Fri, Feb 27, 2026 at 11:24 PM Yagnatinsky, Mark via log4j-user < [email protected]> wrote: > In several places in Loader, such as here: > > https://github.com/apache/logging-log4j2/blob/2.x/log4j-core/src/main/java/org/apache/logging/log4j/core/util/Loader.java#L94 > There's a message at trace level saying basically "Trying to find > [FILENAME] using THINGY". > This is very useful, because it lets you know all the places that log4j is > looking for config files. > However, there's no good way to find which of these attempts succeeded. > Earlier today I had to put a debug breakpoint inside this class to find > out which log4j2.xml was getting loaded. > It would be nice if successful attempts were logged, perhaps even at a > level higher than trace. (maybe debug??) > > Thoughts? > > ________________________________ > > The information contained in this message is intended only for the > recipient, and may be a confidential attorney-client communication or may > otherwise be privileged and confidential and protected from disclosure. If > the reader of this message is not the intended recipient, or an employee or > agent responsible for delivering this message to the intended recipient, > please be aware that any dissemination or copying of this communication is > strictly prohibited. If you have received this communication in error, > please immediately notify us by replying to the message and deleting it > from your computer. S&P Global Inc. reserves the right, subject to > applicable local law, to monitor, review and process the content of any > electronic message or information sent to or from S&P Global Inc. e-mail > addresses without informing the sender or recipient of the message. By > sending electronic message or information to S&P Global Inc. e-mail > addresses you, as the sender, are consenting to S&P Global Inc. processing > any of your personal data therein. >
