Help Desk Ticket Reference: https://na7.salesforce.com/500A0000005ezKT
project_key: JBEPP

conf/organization/idm-configuration.xml currently defines the following hibernate.properties:
 
        <name>hibernate.properties</name>
        <description>Default Hibernate Service</description>
        <property name="hibernate.cache.region.jbc2.query.localonly" value="true" />
        <property name="hibernate.cache.region.factory_class" value="org.hibernate.cache.jbc2.MultiplexedJBossCacheRegionFactory"

This results in two cache instances (entity-cache and timestamp-cache) being used, defined in hibernate-jbosscache2.jar/org/hibernate/cache/jbc2/builder/jbc2-configs.xml and set up with JGroups stack 'udp', even if the server is started with -Djboss.default.jgroups.stack=tcp:

2011-01-10 11:37:08,037 DEBUG [org.jboss.cache.RPCManagerImpl] (main) Created Multiplexer Channel for cache cluster optimistic-entity using stack udp
---------------------------------------------------------
GMS: address is 127.0.0.1:52612 (cluster=udp)
---------------------------------------------------------
2011-01-10 11:37:10,160 DEBUG [org.jboss.cache.RPCManagerImpl] (main) Created Multiplexer Channel for cache cluster timestamp-cache using stack udp

According to [1],  org.hibernate.cache.jbc2.JndiMultiplexedJBossCacheRegionFactory is best to be used inside JBoss AS. Therefore, the above configuration should be changed to:

        <name>hibernate.properties</name>
        <description>Default Hibernate Service</description>
        <property name="hibernate.cache.region.jbc2.query.localonly" value="true" />
        <property name="hibernate.cache.region.jbc2.cachefactory" value="java:CacheManager"/>
        <property name="hibernate.cache.region.factory_class" value="org.hibernate.cache.jbc2.JndiMultiplexedJBossCacheRegionFactory" />

With this configuration, the JBoss Cache instances are created as defined in deploy/cluster/jboss-cache-manager.sar/META-INF/jboss-cache-manager-jboss-beans.xml, where the 'jboss.partition.name' and 'jboss.default.jgroups.stack' startup options are properly incorporated.

[1] http://docs.jboss.org/jbossclustering/cluster_guide/5.1/html/clustering-entity.html