I've been seeing this kind of thing quite a bit in logs from testsuite runs; seems to correspond to intermittent increase in clustering failures: | 2008-04-10 13:58:28,949 ERROR [org.jboss.cache.remoting.jgroups.CacheMessageListener] (Multiplexer,udp,10.18.34.175:51700) Caught org.apache.commons.logging.LogConfigurationException while responding to state transfer request | org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable. | at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:798) | at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:601) | at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:333) | at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:664) | at org.jboss.cache.statetransfer.DefaultStateTransferGenerator.<init>(DefaultStateTransferGenerator.java:32) | at org.jboss.cache.statetransfer.StateTransferFactory.getStateTransferGenerator(StateTransferFactory.java:43) | at org.jboss.cache.statetransfer.StateTransferManager.getStateTransferGenerator(StateTransferManager.java:297) | at org.jboss.cache.statetransfer.StateTransferManager.getState(StateTransferManager.java:82) | at org.jboss.cache.remoting.jgroups.CacheMessageListener.getState(CacheMessageListener.java:137) | at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUpEvent(MessageDispatcher.java:629) | at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:747) | at org.jgroups.JChannel.up(JChannel.java:1154) | at org.jgroups.mux.Multiplexer$Task.run(Multiplexer.java:1175) | at org.jgroups.mux.Multiplexer$ExecuteTask.run(Multiplexer.java:1198) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) | at java.lang.Thread.run(Thread.java:595) | I'm going to turn on commons-logging's diagnostic logging feature for the cluster-udp-0 and cluster-udp-1 configs; hopefully that will shed some light on what's causing this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143331#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...