@danberindei That's not as simple as it sounds. There are tests in the core/ testsuite that verify cache manager restart processes, and they assume that a cache manager can be restarted. Originally this was added in order to enable cache manager restarts via JMX/RHQ and as a result one of the key things done is leave the MBeans registered even if the cache manager stops.

For JCache cache manager, forcing its status to be terminated and not allowing it to be restarted would be fine IMO, it's what the spec expects and tests in the TCK too.