[
https://issues.apache.org/jira/browse/LOG4J2-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484755#comment-17484755
]
Jitin Dominic edited comment on LOG4J2-3381 at 1/31/22, 4:05 PM:
-----------------------------------------------------------------
[~rgoers]
Here's my _log4j2.properties_ file:
{code:java}
rootLogger.level = INFO
rootLogger.appenderRefs = stdout
rootLogger.appenderRef.stdout.ref = STDOUT
appender.console.type = Console
appender.console.name = STDOUT
appender.console.layout.type = PatternLayout
appender.console.layout.pattern = %m%n {code}
was (Author: JIRAUSER283874):
Here's my _log4j2.properties_ file:
{code:java}
rootLogger.level = INFO
rootLogger.appenderRefs = stdout
rootLogger.appenderRef.stdout.ref = STDOUT
appender.console.type = Console
appender.console.name = STDOUT
appender.console.layout.type = PatternLayout
appender.console.layout.pattern = %m%n {code}
> 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)
