-
Bug
-
Resolution: Done
-
Critical
-
16.0.0.Final
-
None
Consider the following code:
AtomicInteger value = new AtomicInteger(1);
session.setAttribute("a", value);
value.incrementAndGet();
On failover, the value of attribute "a" will still be 1.
- clones
-
WFLY-11884 Mutations following HttpSession.setAttribute(...) lost on failover when using ATTRIBUTE granularity distributed web session with a non-transactional cache
- Closed