Maybe WebLogic bundles Log4j2 as a server module already? Some other EE
container servers do that.
On Tue, Jun 4, 2019 at 11:46, Ralph Goers
wrote:
> I am also unclear as to why this would be any different than any other
> servlet container. I recall having seen an issue where the
> contextIniti
I am also unclear as to why this would be any different than any other servlet
container. I recall having seen an issue where the contextInitialized method of
Log4jServletContextListener was not being called. I don’t believe we ever
determined why it wasn’t happening.
Ralph
> On Jun 4, 2019, a
I'm not sure if any of the developers here are using WebLogic. Do you
think you can provide some sort of functional test or integration test
that demonstrates the problem?
On Tue, 4 Jun 2019 at 04:25, Gaurav wrote:
>
> The log4j2's web lookup - ${web:rootDir} seems to cause problems on weblogic
The log4j2's web lookup - ${web:rootDir} seems to cause problems on weblogic
12c deployment.
I suspect that the log4j2 web-lookup plugin is not initialized when weblogic
requests the logger at the start of deployment and is unable to create the file.
Details in the apache issue link and stackov
