-
Bug
-
Resolution: Obsolete
-
Critical
-
None
-
7.2.1.GA
-
None
Customer is running into an issue where JSF is holding a lock on an object while calling HttpSession.setAttribute on that object. That lock is blocking the session replication, which occurs during the setAttribute call when using the READ_COMMITTED/non-BATCH
cache configuration to allow multiple requests to the same session at once.
- clones
-
JBEAP-18111 [GSS](7.2.z) JSF is Holding a Lock on an Object While Calling HttpSession.setAttribute on that Object.
- Verified