I'm going to drop commons-logging in favor of JDK logging in JGroups
3.0. -1 JAR, which is excellent. So I only ship jgroups.jar.
Maybe I'm going to see the days when I download JBC and only download 1
JAR: jboss-cache.jar... :-)
No, didn't think so !
Jason T. Greene wrote:
Last night I updated both pojo and core to use a non-ancient
commons-logging release. This fixed a really annoying performance
problem where it enables TRACE logging when your loglevel is set to
Also it fixes CL leaks.
However, I think at some point we should drop commons-logging in favor
a) JDK logging
b) JBoss logging
JBoss logging can use log4j or jdk logging as a backend.
Lead JGroups / Clustering Team
JBoss - a division of Red Hat