[jboss-jira] [JBoss JIRA] (JBJCA-1294) caching the value of isTraceEnabled
RH Bugzilla Integration (JIRA)
issues at jboss.org
Wed Oct 7 15:10:00 EDT 2015
[ https://issues.jboss.org/browse/JBJCA-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
RH Bugzilla Integration updated JBJCA-1294:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1259840
Bugzilla Update: Perform
> caching the value of isTraceEnabled
> -----------------------------------
>
> Key: JBJCA-1294
> URL: https://issues.jboss.org/browse/JBJCA-1294
> Project: IronJacamar
> Issue Type: Bug
> Affects Versions: 1.2.6.Final
> Reporter: Johnathon Lee
> Assignee: Jesper Pedersen
>
> 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:
> grep 'log.isTraceEnabled();' -r * --include='*.java'
> Replacement of all if (trace) with calls to log.tracef would be needed.
> 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
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list