This content has been marked as final.
Show 2 replies
-
1. Re: Distributed sessions and batching
pferraro Jun 21, 2014 3:06 PM (in response to ron.leisti)While pessimistic locking is the default behavior, you can configure the infinispan cache to use optimistic locking instead - in which case, locks will be acquired only when the batch is closed (i.e. at the end of the request). You will also need to modify the transaction isolation to use READ_COMMITTED (instead of REPEATABLE_READ, the default) - otherwise, concurrent acess will result in write skews since each request updates the last modified timestamp.
-
2. Re: Distributed sessions and batching
pferraro Jun 21, 2014 3:09 PM (in response to pferraro)I should also add that the purpose of the default behavior is to prevent concurrent access to a session by multiple nodes, which is explicitly forbidden by the servlet spec.