[jboss-dev-forums] [Design of JBossCache] - Re: Too much jboss cache INFO logging

[bstansberry@jboss.com]

:-)

INFO is good only if it's quite likely to save a round trip back and forth with a customer on a support case to get config info.  Of the 3 types of logging in Dimitris' snippet, the only one that comes up routinely is the version logging.  That IMHO is OK at INFO, but really should just be a corporate policy thing -- i.e. if we decide across JBoss not to log versions at INFO, JBC shouldn't; if it's OK to do it at info, then JBC should, since it comes up so often.

The "12:34:59,968 INFO  [DefaultPartition-TomcatCache] Using marshaller org.jboss.cache.marshall.VersionAwareMarshaller" info can easily be deduced by looking at a config file.  It's not something that comes up often either; maybe never.

The interceptor chain factory stuff is harder; i.e. takes *some* effort to figure out the chain from a config file, and knowing the chain is important in some tricky cases.  But, 90% of the benefit could be achieved just by adding a wiki page that shows what the chains look like in the standard setups:

PESSIMISTIC, no cacheloader
OPTIMISTIC, no cacheloader

PESSIMISTIC, cacheloader w/ passivation=false
OPTIMISTIC, cacheloader w/ passivation=false

PESSIMISTIC, cacheloader w/ passivation=true
OPTIMISTIC, cacheloader w/ passivation=true

(Include DataGravitationInterceptor in all with a comment about how it's not there if buddy replication isn't enabled. Same for CacheMgmtInterceptor.)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067918#4067918

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067918