[infinispan-dev] trace vs log.isTraceEnabled

Manik Surtani manik at jboss.org
Wed Dec 7 11:15:44 EST 2011


Sanne, 

+1 to consistency.  I suggest we repurpose https://issues.jboss.org/browse/ISPN-1429 to a consistent logging scheme.  My preference is for a static final boolean trace = log.isTraceEnabled().

But I do see Erik's concerns about wanting to switch on tracing on the fly.

- Manik

On 7 Dec 2011, at 13:45, Sanne Grinovero wrote:

> On 7 December 2011 13:38, Erik Salter (esalter) <esalter at cisco.com> wrote:
>> +1 in trace log consistency.  We've noticed this in trying to gather
>> logs in running down bugs.  I'd rather NOT have to restart, since most
>> of the problems I need trace logs for don't show up until a system has
>> been running for a while.
>> 
>> Regards,
>> 
>> Erik
> 
> thanks Erik, you make a good point. But those logs which are currently
> using a constant likely need to stay as they are, as they would
> otherwise slow down significantly, so while I'm voting for consistency
> I wouldn't like to go in that direction :)
> We need an agent, I see no other solution.
> 
> Sanne
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20111207/3efe0368/attachment.html 


More information about the infinispan-dev mailing list