Log4j configuration with no root level causes NPE in Log4jLogger.java

Description

From xeno6...@gmail.com on May 01, 2014 08:17:02

What steps will reproduce the problem? 1. Configure log4j to NOT have a root Level
2. Make an esapi logging call that WOULD normally fall through to the root logger, but does not. What is the expected output? What do you see instead? We would expect to see nothing--with no level configuration on the root logger we expect calls that would fall through to be silent, however we get an NPE. What version of the product are you using? On what operating system? 2.1.0 on Windows && RedHat Does this issue affect only a specified browser or set of browsers? No. Please provide any additional information below. Attached a patch for fix.

Attachment: log4j_patch.txt

Original issue: http://code.google.com/p/owasp-esapi-java/issues/detail?id=327

Environment

None

Status

Assignee

Unassigned

Reporter

Max Gelman

Priority

Configure