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

Bug in log4j configuration #139

Open
GoogleCodeExporter opened this issue Mar 21, 2015 · 1 comment
Open

Bug in log4j configuration #139

GoogleCodeExporter opened this issue Mar 21, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?

Run the attached program.

What is the expected output? What do you see instead?

To see the bug, first run the app as is, then uncomment the commented line in 
the logging.properties file. In the first case, the ascii art will be printed, 
in the 2nd case it will not be printed while it should be printed.

Please use labels and text to provide additional information.

See also 
https://groups.google.com/forum/?fromgroups=#!topic/as3-commons-developers/SBJ1M
WFVzEo for more info.

Original issue reported on code.google.com by wim.debl...@gmail.com on 26 Mar 2013 at 4:17

Attachments:

@GoogleCodeExporter
Copy link
Author

I tried some more things and I found that using this triggers the bug:

log4j.logger.com.company.log4jtest.testpackage=FATAL
log4j.logger.com.company=INFO

However, adding an extra line makes the bug go away:

log4j.logger.com.company.log4jtest.testpackage=FATAL
# Add this line as workaround
log4j.logger.com.company.log4jtest=INFO
log4j.logger.com.company=INFO

Original comment by wim.debl...@gmail.com on 26 Mar 2013 at 4:17

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