In any case, whatever we decide, we (a) need something in place and (b) need it fast (pre-5.2.2), so that it is in JDG 6.1.GA.
Do we have a JIRA for this? - M On 20 Feb 2013, at 13:01, Radim Vansa <rva...@redhat.com> wrote: > I'd rather alter the toString behaviour with -Dinfinispan.commands.debug than > the log verbosity level. > You have precedent in org.infinispan.util.Util.printArray > (-Dinfinispan.arrays.debug) used by ByteArrayKey.toString > > Radim > > ----- Original Message ----- > | From: "Adrian Nistor" <anis...@redhat.com> > | > | What if we include that verbose info in toString() only if trace is > | enabled? :) > | > | On 02/20/2013 02:36 PM, Dan Berindei wrote: > | > | > | Yeah, we couldn't introduce a RpcDispatcher.includeCacheEntries > | category anyway because the cache entries are included in the > | command's toString() - the logger can't do anything to filter them > | out. > | > | > | I think we could eliminate the cache entries from > | StateResponseCommand.toString() (and the segment owners from > | ConsistentHash.toString()), and only log them separately, under a > | different category/class name. > | > _______________________________________________ > infinispan-dev mailing list > infinispan-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani ma...@jboss.org twitter.com/maniksurtani Platform Architect, JBoss Data Grid http://red.ht/data-grid _______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
