Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
11.0.3.Final
-
None
-
- Deploy ISPN-12207.war
to any Servlet container (e.g. Wildfly) with at least 2 nodes - Navigate to http://<domain>/ISPN-12207/get.jsp in node 1 (this will generate the initial data and put to the cache, note invalidation cache will call `putForExternalRead()` instead
- Navigate to http://<domain>/ISPN-12207/get.jsp in node 2 (similarly, generate initial data)
- Navigate to http://<domain>/ISPN-12207/remove.jsp in node 1, to evict the cache data
- Navigate to http://<domain>/ISPN-12207/get.jsp in node 2, expecting invalidation cache data got regenerated, but actually still keeping the previous data
- Navigate to http://<domain>/ISPN-12207/update.jsp in node 1, to force regenerate data and put to the cache (invalidation cache also will call `put()` instead of `putForExternalRead()`)
- Navigate to http://<domain>/ISPN-12207/get.jsp in node 2, expecting invalidation cache data got regenerated, but actually still keeping the previous data
Deploy ISPN-12207.war to any Servlet container (e.g. Wildfly) with at least 2 nodes Navigate to http://<domain>/ ISPN-12207 /get.jsp in node 1 (this will generate the initial data and put to the cache, note invalidation cache will call `putForExternalRead()` instead Navigate to http://<domain>/ ISPN-12207 /get.jsp in node 2 (similarly, generate initial data) Navigate to http://<domain>/ ISPN-12207 /remove.jsp in node 1, to evict the cache data Navigate to http://<domain>/ ISPN-12207 /get.jsp in node 2, expecting invalidation cache data got regenerated, but actually still keeping the previous data Navigate to http://<domain>/ ISPN-12207 /update.jsp in node 1, to force regenerate data and put to the cache (invalidation cache also will call `put()` instead of `putForExternalRead()`) Navigate to http://<domain>/ ISPN-12207 /get.jsp in node 2, expecting invalidation cache data got regenerated, but actually still keeping the previous data - Deploy ISPN-12207.war
Description
Functional Map API not working properly when working with invalidation cache. When in a clustered environment, expecting cache put and cache remove will notify cluster members to do cache eviction when dealing when invalidation cache. But observed no cache eviction occurred in cluster members when using Functional Map APIs to deal with invalidation cache.
