Dan Berindei created ISPN-1852: ---------------------------------- Summary: If a global component fails to start during cache startup, future getCache calls for that cache will never return Key: ISPN-1852 URL: https://issues.jboss.org/browse/ISPN-1852 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.1.1.FINAL Reporter: Dan Berindei Assignee: Dan Berindei Priority: Critical Fix For: 5.1.2.CR1 In DefaultCacheManager, before starting a cache we register a CacheWrapper with the cache name, and subsequent calls to getCache(cacheName) will wait for a countdown latch in the CacheWrapper to confirm that the cache has finished starting. However, if a global component fails to start, that latch is never opened - so future calls to getCache(cacheName) will block forever. If startCaches() is used to start multiple caches at once, the global start exception will be on a background thread and the user will only notice that the getCache calls on the main thread never return. This situation appeared in the hibernate-search test suite, which extended JGroupsTransport to change the cluster name to a unique value on startup. The cluster name is not dynamic in 5.1, so the global component registry failed to start. -- 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