"clebert.suconic(a)jboss.com" wrote : | Still better to not call it when trace is not set IMO. Yes, log.isTraceEnabled() has a significant overhead. Actually in JBM 1.4 approx 3% of time was spent in log.isTraceEnabled() calls until we changed it to check a static flag "trace"! (Admittedly we had a lot of log.isTraceEnabled() calls). Moral of the story: Don't assume that log.isTraceEnabled() (or log.isDebugEnabled()) is a fast call, and never put it in performance critical sections. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150602#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...