-
Bug
-
Resolution: Obsolete
-
Critical
-
None
-
7.1.6.GA
-
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
-
JBEAP-16585 (7.2.z) WFLY-11884 - Mutations following HttpSession.setAttribute(...) lost on failover when using ATTRIBUTE granularity distributed web session with a non-transactional cache
- Closed