[jboss-jira] [JBoss JIRA] (AS7-3290) second level cache is not working after upgrading to Hibernate 4.0.1 (NPE in org.hibernate.cache.infinispan.InfinispanRegionFactory.getCache)

[ https://issues.jboss.org/browse/AS7-3290?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-3290: ----------------------------------- <smarlow> galderz: which code module contains the code for constructing the global component registry (that gets Infinispan core to load the Hibernate Infinispan service entries)? <ttarrant> smarlow, the module that constructs that is org.jboss.as.clustering.infinispan <ttarrant> smarlow, the gcr is constructed with that module's classloader <ttarrant> smarlow, you probably need to add hibernate-infinispan to that module <ttarrant> with services exported <ttarrant> smarlow, can you try ? <smarlow> ttarrant, galderz: org.jboss.as.clustering.infinispan doesn't really know about the Hibernate Infinispan module, but even if org.jboss.as.clustering.infinispan had a dependency on Hibernate Infinispan, I'm not sure what that would do but I can try it as a hacj <ttarrant> smarlow, you are consuming caches created by the infinispan clustering subsystem are you not ? <smarlow> ttarrant: yes <smarlow> I believe that is the case <ttarrant> smarlow, the infinispan GlobalConfigurationRegistry is initialized by that subsystem with its module's classloader <ttarrant> smarlow, therefore the ServiceLoader will find only the services "exported" at that level <ttarrant> and visible to that classloader * smarlow is adding <module name="org.hibernate.infinispan" services="export"/> to org.jboss.as.clustering.infinispan <smarlow> ttarrant, galderz: ^ worked! :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira