Fix Issue 'NoSuchFieldError: TRACE' from log4j #40
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…/lib for jars
Agent with different FABAN_HOME than master would not find serice jars because it scanned ${ServiceName} and not ${ServiceName}/lib. Agent now scans ${ServiceName}/lib/
log4j-1.2.8 does not include a TRACE Level which causes errors loading classes that use log.tracef(). The TRACE level was added in 1.2.11 but updating to the latest 1.2.17. harness passes unit testing (run-tests)
Changed the return type to HttpClient based on changes to internal API. This might be a compatibility issue.
shanti
added a commit
that referenced
this pull request
Nov 5, 2012
Fix Issue 'NoSuchFieldError: TRACE' from log4j
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
the packaged version of log4j does not include a TRACE level which causes errors for classes that use log.tracef() or any other trace level logging. The problem occurred when running a Service class on the master (where faban.war is deployed) and was resolved by updating to the latest log4j (1.2.17).
Harness passes all existing unit tests with the new log4j version.