EJBCLIENT-126 Use Message Format Patterns #85
Merged
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
Most of the JBoss code uses message format patterns for debug logging in order to avoid unnecessary allocations in normal operation. The JBoss EJB client seems to be one of the few places where this is not yet the case and debug messages are always created even if the debug logging is disabled. * use `#debugf` for debug logging * use `#isDebugEnabled` for debug statements too complex for `#debugf` Issue: EJBCLIENT-126 https://issues.jboss.org/browse/EJBCLIENT-126
dmlloyd
added a commit
that referenced
this pull request
Jan 6, 2015
…dFly-8.1.0.Final_EAP_6.3.0 Add versions for WildFly 8.1.0.Final and EAP 6.3.0
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.
Most of the JBoss code uses message format patterns for debug logging
in order to avoid unnecessary allocations in normal operation. The
JBoss EJB client seems to be one of the few places where this is not
yet the case and debug messages are always created even if the debug
logging is disabled.
#debugffor debug logging#isDebugEnabledfor debug statements too complex for#debugfIssue: EJBCLIENT-126
https://issues.jboss.org/browse/EJBCLIENT-126