I dont know if this helps or not but we ran into a similar issue testing the distributed cache with Shiro authentication. Shiro was eagerly trying to create the cache but the Spring Ignite instance (inside the SpringCacheManager) had not yet been initialized (I believe it initializes after all the beans are configured).
In our case, we wrapped the "cache" with a Provider<> so that we could lazily access it when needed after everything started up. ----- KJQ -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
