[ https://issues.jboss.org/browse/WFLY-6554?page=com.atlassian.jira.plugin.... ] Mathieu Lachance commented on WFLY-6554: ---------------------------------------- Hi [~pferraro], sorry for taking so long, but I've found the NPE issue I was having. We use a stripped down version of standalone.xml. Since we are relying on Spring for the EntityManager bootstrapping, we excluded the JPA subsystem. By excluding that subsystem, the org.jboss.as.jpa.processor.secondLevelCache.CacheDeploymentListener SPI was not available within the classpath, hence: {code} try { // start a private cache for non-JPA use and return the started cache. wrapper = Notification.startCache(Classification.INFINISPAN, cacheSettings); return (EmbeddedCacheManager)wrapper.getValue(); } catch (Exception e) { throw new CacheException(e); } public static Wrapper startCache(Classification cacheType, Properties properties) throws Exception { Wrapper result = null; for(EventListener eventListener: eventListeners) { Wrapper value = eventListener.startCache(cacheType, properties); if (value != null && result == null) { result = value; // return the first non-null wrapper value returned from a listener } } return result; } {code} wrapper was always null, since there was no listener at all. I know our use case might be a little bit weird but maybe there's some validation or warning missing around here? That said, after that I was able to use the 'org.jboss.as.jpa.hibernate5.infinispan.InfinispanRegionFactory' without any exception. There's still one problem though, all the caches configuration are still not yet defined properly. All my "entity" cache inherit from the default cache i.e. "local-query". I've also tried the 'org.jboss.as.jpa.hibernate5.infinispan.SharedInfinispanRegionFactory' but got also the exact same behavior. Could it be possible that the configuration is picked up from inside one of the hibernate jars instead of the one defined in the infinispan subsystem? -- This message was sent by Atlassian JIRA (v6.4.11#64026)