[
https://issues.redhat.com/browse/WFLY-13238?page=com.atlassian.jira.plugi...
]
Paul Ferraro updated WFLY-13238:
--------------------------------
Description:
Consider the following:
{code:java}
session.setAttribute("foo", new AtomicInteger(0));
AtomicInteger value = (AtomicInteger) session.getAttribute("foo");
value.incrementAndGet();
{code}
When request is receive on a non-primary owner, the above code does not correctly
replicate the mutated value when using ATTRIBUTE granularity and the backing cache in
non-transactional.
was:
Consider the following:
{code:java}
session.setAttribute("foo", new AtomicInteger(0));
AtomicInteger value = (AtomicInteger) session.getAttribute("foo");
value.incrementAndGet();
{code}
When t
Object returned by HttpSession.getAttribute(...) following a previous
setAttribute(...), not mutating correctly on non-primary owner using ATTRIBUTE granularity
when cache is non-transactional.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-13238
URL:
https://issues.redhat.com/browse/WFLY-13238
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 19.0.0.Beta3
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Priority: Critical
Consider the following:
{code:java}
session.setAttribute("foo", new AtomicInteger(0));
AtomicInteger value = (AtomicInteger) session.getAttribute("foo");
value.incrementAndGet();
{code}
When request is receive on a non-primary owner, the above code does not correctly
replicate the mutated value when using ATTRIBUTE granularity and the backing cache in
non-transactional.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)