You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2021/12/22 18:35:00 UTC
[jira] [Commented] (LOG4J2-3251) Weblookup ${web:rootDir} is not working if old loggercontext is removed and tried to initialize loggerContext using Configurator.initialize
[ https://issues.apache.org/jira/browse/LOG4J2-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464000#comment-17464000 ]
Gary D. Gregory commented on LOG4J2-3251:
-----------------------------------------
If you get an NPE, it would be nice to have it FTR.
> Weblookup ${web:rootDir} is not working if old loggercontext is removed and tried to initialize loggerContext using Configurator.initialize
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-3251
> URL: https://issues.apache.org/jira/browse/LOG4J2-3251
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.15.0, 2.16.0
> Reporter: Sankalp
> Priority: Blocker
> Labels: weblookup
> Attachments: console.log
>
>
> In a web application, I am first creating a loggerContext and it log4j.xml has ${web:rootDir} for lookup. It is resolved as expected.
> I am removing the older loggerContext and using Configurator.initialize(contextName, classlodaer, filePaths, context). This API fails and I can observe that inside weblookup it is NOT getting servletContext. Below API returns null.
> *ServletContext ctx = WebLoggerContextUtils.getServletContext();*
--
This message was sent by Atlassian Jira
(v8.20.1#820001)