bshaw wrote:
Short Answer: JBoss 4.0.0
Long Answer: I am not running this test in the JBoss container. I just included all JBoss jar files (that was shipped along with Hibernate) in the class path. Would that be a problem? Hibernate In Action books says all JBoss server specific configuration would be simply ignored in a non-Jboss environment.
Also, since the cache usage is set to transactional, I thought may be this would work only in an managed environment. So I tried running this under Weblogic 8.1 (again with Jboss jars in the classpath), no luck there either. Container or no container, I get the same error.
<ClusterConfig> attribute is a jgroups configuration which is used by treecache as transport layer, no matter in jboss or standalone. I've just cut-n-paste your quoted config to my jboss-cache.xml config and no errors appeared. Visually I see no difference with my own config.
I suggest you take jboss-cache.jar and jgroups.jar whether from the latest treecache distribution or jboss distribution (I've just tried in jboss-3.2.6 release and it's ok) because they could by outdated in hibernate distrib (in particulary jgroups.jar)