-
Bug
-
Resolution: Done
-
Critical
-
19.0.0.Beta3
Consider the following:
session.setAttribute("foo", new AtomicInteger(0)); AtomicInteger value = (AtomicInteger) session.getAttribute("foo"); value.incrementAndGet();
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.
- clones
-
JBEAP-18951 [GSS](7.3.z) Object returned by HttpSession.getAttribute(...) following a previous setAttribute(...), not mutating correctly using ATTRIBUTE granularity when cache is non-transactional.
- Closed