Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ConcurrentMapCacheManager has interdependent setters [SPR-12026] #16642

spring-projects-issues opened this issue Jul 24, 2014 · 1 comment
in: core type: enhancement


Copy link

@spring-projects-issues spring-projects-issues commented Jul 24, 2014

Oliver Drotbohm opened SPR-12026 and commented

ConcurrentMapCacheManager's setCacheNames(…) transitively calls isAllowNullValues() which can be influenced by setAllowNullValues(…). This means the order of the setter calls becomes important and is not guaranteed when the type is used in XML configuration.

We've got a similar issue reported for Spring Data Redis (see DATAREDIS-328) and decided to provide a dedicated FactoryBean for usage in XML.

Affects: 3.2.10, 4.0.6, 4.1 RC1

Issue Links:

  • #16736 GuavaCacheManager ignores cache specification due to eager initialization of internal cache map with static cache names
  • DATAREDIS-328 RedisCacheManager should not instantiate caches in setCacheNames()

Referenced from: commits acbd61b, 7848412

Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jul 24, 2014

Juergen Hoeller commented

ConcurrentMapCacheManager recreates existing caches in case of a setAllowNullValues change now. To be backported to 4.0.7 as well.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
in: core type: enhancement
None yet

No branches or pull requests

2 participants