Shiro and Spring integration times versions of Ehcache before version 2.5 allowed any number of cachemanagers with the same name (same config Uration Resource) to exist in a JVM.

Shiro is integrated with spring and has been reported another unnamed CacheManager already exists in the same VM. Provide unique names for each cachemanager in the config or do one of the following:
1. Use one of the cachemanager.create () static factory methods to reuse same CacheManager with same name or create one if Necessary
2. Shutdown the earlier CacheManager before creating new one with same name.
The source of the existing CacheManager is:inputstreamconfigurationsource [[email protected]]

Workaround: The Ehcache jar package was changed to 2.5 before, because 2.5 CacheManager used a single case.

By the way, and now Baidu a bit of a problem, a uniform answer, all copy others, did not explain not to mention the source.

There is a need to see the blogger said the reason, the address is: http://blog.csdn.net/u013147600/article/details/48133913

Shiro and Spring integration times versions of Ehcache before version 2.5 allowed any number of cachemanagers with the same name (same config Uration Resource) to exist in a JVM.