[
https://issues.apache.org/jira/browse/LOG4J2-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269676#comment-17269676
]
Robert Turner commented on LOG4J2-2624:
---------------------------------------
Tim:
I'm not part of the log4j team, but the general idea of using a
{{ServletContextListener}} was what I had tried a while ago in my local tests,
but I hadn't quite gotten it to work (I think because I was trying to rely on a
{{ServletContainerInitializer}} to perform the general initialization. I had
only been trying it out on our local app, so I never got around to trying to
work through the problem in more detail. However, I think the general approach
is correct based on my investigation almost 2 years ago.
Also, if you "format" your comment on the Jira using the markup in Jira, it
would make the code examples a lot easier to read. That might help people
review it more easily.
> ${web:rootDir} not working in weblogic 12c
> ------------------------------------------
>
> Key: LOG4J2-2624
> URL: https://issues.apache.org/jira/browse/LOG4J2-2624
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.11.0
> Reporter: gaurav
> Priority: Blocker
>
> The web lookup - ${web:rootDir} seems to cause problems on weblogic 12c
> deployment.
> I suspect that the _*web-lookup plugin is not initialized*_ when weblogic
> requests the logger at the start of deployment and is unable to create the
> file.
> What I've done -
> *1. Added slf4j in weblogic preferred packages of weblogic.xml.*
> <wls:package-name>org.slf4j.*</wls:package-name>
> *2. log4j-web dependency is present in classpath.*
> *3.web.xml contains following:-*
> <context-param>
> <param-name>isLog4jAutoInitializationDisabled</param-name>
> <param-value>true</param-value>
> </context-param>
> <listener>
>
> <listener-class>org.apache.logging.log4j.web.Log4jServletContextListener</listener-class>
> </listener>
> <filter>
> <filter-name>log4jServletFilter</filter-name>
>
> <filter-class>org.apache.logging.log4j.web.Log4jServletFilter</filter-class>
> </filter>
> <filter-mapping>
> <filter-name>log4jServletFilter</filter-name>
> <url-pattern>/*</url-pattern>
> <dispatcher>REQUEST</dispatcher>
> <dispatcher>FORWARD</dispatcher>
> <dispatcher>INCLUDE</dispatcher>
> <dispatcher>ERROR</dispatcher>
> </filter-mapping>
> *Note - Log4jServletContextListener is placed before all listeners.
> -Have attached stacktrace for your reference.
> [^stacktrace.txt]
> Please assist.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
