Am 27.04.11 16:55, schrieb Mircea Markus:
Hi,
I'm looking into some logs for the a JBW demo : it has 4 caches deployed on each node
and lots of topology changes happen. It's close to impossible to tell which log
pertains to which cache, especially around the DistributionInterceptorImpl.
Wouldn't it make sense that, for certain components, to include the name of the cache
in the logs? IThis might be achieved with minimal changes by adding an additional param to
the LogFactory.getLog(Class) method and let the logger itself do the heavy lifting.
e.g.
Log l = LogFactory.getLog(DistributionManagerImpl.class, "cacheName");
and on each call l.trace("A message") the logger might output, besides
underlying log's format, the string "[cacheName] A message".
I would prefer a largely transparent mechanism base on MDC[1], yet it
seems as if Inifispan's own log abstraction does not support this.
Which in turn leads me to a question I wanted to ask anyway. Why does
Infinispan have its own logging abstraction when there is jboss logging?
Wdyt?
Cheers,
Mircea
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev