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.