-
-
Notifications
You must be signed in to change notification settings - Fork 174
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
Failed to instantiate [ch.qos.logback.classic.LoggerContext] #66
Comments
Resolved. |
Followup note: (possible bug?) If a config.xml uses 'includes' to load settings from another child config [Note: This seems odd since we could use 'includes' to replicate the legacy logback-test.xml versus logback.xml loading approach where, presumably, those xml's would have 'configuration' tagged blocks.] Example:
The child [apparently] needs to omit the 'configuration' tag else the closing tag in the child xml will also close the parsing in the parent such that anything after the 'includes' will fail. If debug="true" then will see "no applicable action" messages for otherwise valid logcat entries. assets/logback-child.xml
|
I can't reproduce the problem with loading the child config. I might be missing a step. Can you create a new issue for this problem? Please add some details to reproduce the problem. Thanks. Note that when using |
[Hopefully re-opening this issue is okay? I could create another. But same topic and history of previous comments kept together. Plus, my 'resolution' above wasn't really a proper solve for my original problem anyway.]
Unable to attach files so pasted content in this post below.
I can zip up the entire android project and mail to you as well if that would help. ~~ logback.xml
~~ logback-works.xml
~~ logback-fails_Con.xml
~~ logback-fails_Inc.xml
~~ Logcat output from running app three times in a row
|
A configuration error occurred when an included configuration was enclosed in a <configuration> or <included> tag. The closing tag of that enclosure was not detected and thus not removed from the XML doc, which caused it to propagate to the parent config, leading to an XML parsing error. This was seen as a confusing error to the user: Failed to instantiate [ch.qos.logback.classic.LoggerContext] The problem was that the SaxEvent's qName was not populated for the closing tag of the included config. However, the localName was properly set. The IncludeAction now checks the qName and falls back to localName if needed. Fixes Issue #66
Thanks for the details. I found the bug, and it should be fixed now in 7916e7e. |
Yay! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hi Tony,
I've used logback in the past with great love. :) Decided to update to latest versions of SLF4J and logback as I am starting another android project.
Searched for answer in this issues list and internet but not found solution yet.
Is there another library required?
~~
logback.xml is a bare bones logcat appender case.
However, running the application gives the following error after parsing the root's appender-ref.
~~
Any help appreciated - Thanks!
The text was updated successfully, but these errors were encountered: