[
https://issues.redhat.com/browse/ISPN-12207?page=com.atlassian.jira.plugi...
]
Sammy Chu updated ISPN-12207:
-----------------------------
Steps to Reproduce:
# 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
was:
# 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-1227/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
Functional Map APIs not functional properly with invalidation cache
-------------------------------------------------------------------
Key: ISPN-12207
URL:
https://issues.redhat.com/browse/ISPN-12207
Project: Infinispan
Issue Type: Bug
Components: API, Core
Affects Versions: 11.0.3.Final
Reporter: Sammy Chu
Priority: Critical
Attachments: ISPN-12207.source.zip, ISPN-12207.war
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.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)