Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
meg23 opened this issue Nov 13, 2014 · 1 comment
Closed

Comments

@meg23
Copy link

meg23 commented Nov 13, 2014

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

@meg23
Copy link
Author

meg23 commented Nov 13, 2014

From kevin.w.wall@gmail.com on May 01, 2014 21:25:27

Fixed with revision r1942 .

Status: Fixed
Labels: OpSys-All Component-Logger

@meg23 meg23 closed this as completed Nov 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant