[
https://issues.apache.org/jira/browse/LOG4J2-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485420#comment-17485420
]
Ralph Goers commented on LOG4J2-3381:
-------------------------------------
Once you have called context.setConfiguration() you should not then also call
Configurator.initialize(). setConfiguration() will install your new
configuration and start it. Calling Configurator.initialize() then won't work
because the first thing it will do is stop the configuration and you cannot
initialize a stopped configuration.
You should enable StatusLogger debug logging by setting the log4j2.debug system
property to a value of true.
> Programmatically configuring Log4j2
> -----------------------------------
>
> Key: LOG4J2-3381
> URL: https://issues.apache.org/jira/browse/LOG4J2-3381
> Project: Log4j 2
> Issue Type: Question
> Reporter: Jitin Dominic
> Priority: Major
>
> During upgrading log4j2 in grails 2.5.4 application, I removed all log4j
> 1.2.17 dependencies and added following dependencies pertaining to v2.17.1:
> * log4j-api
> * log4j-core
> * log4j-1.2-api
> * log4j-slf4j-impl
>
> I'm trying to read my _log4j2.properties_ file programmatically. We are using
> PropertyConfigurator.configure() to configure the logger.
>
> But I noticed in the
> [documentation|https://logging.apache.org/log4j/2.x/manual/migration.html]
> that Log4j 1.x bridge has some limitations and we can't use it for
> programmatic configuration.
> Is there any alternative way to configure logger programmatically without
> using PropertyConfigurator?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
