Right - we didn't add any tests to JBC as mux requires an mbean server. As you noted, the old code will run if the mux channel isn't available. I think the AS 5.0 cluster tests do use TreeCache with mux as the cluster suite's cluster-service.xml file specifies a mux dependency for the TreeCache instance used for cluster services. I don't recall mux-specific testing, but I wasn't too involved back then. Jerry, do you recall what can of mux-related testing was added to 1.4? Perhaps something like this would work as a good base: 1) Create an ant patternset of the existing tests we want to run, but now with mux. Idea is to re-use existing tests to confirm functionality of things like state transfer, replication, buddy group formation. 2) Add the mux channel configs to the configs used by those tests. Set it to a system property. AIUI, if the property is not set, the mux config will not work and the cache will fall back on the old protocol stack config. So existing tests still work. 3) Create a new target in build.xml that runs the tests in the patternset from #1. The target sets the system property. Crap -- the mux factory is an mbean -- for this to work the tests need an mbean server. Well, maybe the above will spark an idea from someone else. - Brian jbosscache-dev-bounces(a)lists.jboss.org wrote: Ban