Red Hat Bugzilla – Bug 1259840
[GSS](6.4.z) Remove caching of the value of isTraceEnabled for JCA infrastructure
Last modified: 2017-01-17 06:48:06 EST
Description of problem:
caching the value of isTraceEnabled does not allow for complete dynamic control of the logging level. This has ramifications in support scenarios where diagnostics are needed and the ability to reload an instance to enable TRACE level logging is prohibitive.
see examples of TRACE being cached (similar to below in https://github.com/ironjacamar/ironjacamar/tree/1.0):
grep 'log.isTraceEnabled();' -r * --include='*.java'
Replacement of all if (trace) with calls to log.tracef would be needed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Note, that some "if (trace)" would have to be replaced by if (log.isTraceEnabled()) calls, as they guard multiple lines of code, and even synchronization blocks
Jesper Pedersen <email@example.com> updated the status of jira JBJCA-1294 to Resolved
Jesper Pedersen <firstname.lastname@example.org> updated the status of jira JBJCA-1294 to Closed
verified with EAP 6.4.6.CP.CR2
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.