Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.5.0
-
None
Description
Reported on the dev list[1]. The issue is that the CacheManager.create(Configuration) APIs will always use the same singleton, regardless of whether the provided Configuration defines a cache manager of a different name then the existing singleton. We should use the CacheManager.newInstance(Configuration) APIs, as this will use a singleton per cache manager name. This will keep us from stomping on other cache managers that exist in the environment.