-
Bug
-
Resolution: Done
-
Major
-
10.1.8.Final, 11.0.11.Final, 12.1.7.Final, 13.0.2.Final
-
None
When any component fails to start, AbstractComponentRegistry.start() catches the component exception and stops all the components of the cache.
Waiting for the initial state transfer to finish is done in CacheImpl.start(), which does not stop the component registry on an exception.
This means the cache is unusable (DefaultCacheManager.getCache(name) re-throws the timeout exception from the initial state transfer) but it is still a member of the cluster, and other nodes still send commands to it.
It's even worse if the initial state transfer failed because of a marshalling error: the state transfer will never finish, and other nodes will not be able to join.
- is related to
-
JBEAP-23138 [GSS](7.4.z) ISPN-13461 - Cache should stop if the initial state transfer times out
- Closed
- relates to
-
ISPN-9933 Cache components are not stopped after startup error
- Closed
-
ISPN-10070 DefaultCacheManager should stop components after start failure
- Closed