Weblogic Web Application Level Log4j Not Working (Doc ID 1319872.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle WebLogic Server - Version 10.3.4 and later
Information in this document applies to any platform.
***Checked for relevance on 12-10-2013***

Symptoms

Log4J logging is enabled for both the application and WebLogic Server itself; however, log4j logging isn't working. The following errors are observed in the logs:

<Mar 2, 2011 9:08:34 AM EST> <Notice> <StdErr> <BEA-000000> <log4j:ERROR Could not read configuration file [null].> 
<Mar 2, 2011 9:08:34 AM EST> <Notice> <StdErr> <BEA-000000> <java.lang.NullPointerException>
<Mar 2, 2011 9:08:34 AM EST> <Notice> <StdErr> <BEA-000000> <at java.io.FileInputStream.<init>(FileInputStream.java:103)> 
<Mar 2, 2011 9:08:34 AM EST> <Notice> <StdErr> <BEA-000000> <at java.io.FileInputStream.<init>(FileInputStream.java:66)> 
<Mar 2, 2011 9:08:34 AM EST> <Notice> <StdErr> <BEA-000000> <at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:316)>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms