-
Bug
-
Resolution: Done
-
Major
-
9.4.6.Final, 10.0.0.Final
When a cache fails to start (e.g. because a store is not available on startup), the cache is not registered in DefaultCacheManager's map, and stopping the cache manager does not stop any of the components that already started (or even the component that failed).
E.g. in NonStringKeyPreloadTest, the store is not available on startup, and the threads created by HikariCP on startup (in 9.4.x) are not released. The test also leaks an Agroal thread on master, but that is because the test is keeping the connection pool factory in a static field.
- duplicates
-
ISPN-5550 Failing to start Infinispan, started components like JPACacheStore are not closed
- Closed
- is related to
-
ISPN-13461 Cache should stop if the initial state transfer times out
- Closed
- relates to
-
ISPN-10070 DefaultCacheManager should stop components after start failure
- Closed