In our project we have setup infinipan cache. Below are our xml configuration for locking
useLockStriping = "true"
useLockStriping = "true" property is used to create the default lock pool.
lockAcquisitionTimeout="10000" this is the maximum waiting time to get the lock from the pool before adding the entry in to cache.
Actually this is the default configuration. This is working fine when the number of concurrency access to the cache is less than 10. If the concurrency exceeds then it's the following exception.
org.infinispan.util.concurrent.TimeoutException” (Unable to acquire lock after [10 seconds] on key  for requestor [Thread[http-10.226.32.128-5000-Processor10,5,main]]! Lock held by [(another thread)]).
then we increased the "lockAcquisitionTimeout" to 20 seconds. This is working upto 20 or 30 cuncurrency access. if it's exceeds than it's throwing the same exception.
So we should know if there any way to increase the default lock pool size??
Thanks in advance
Hmmm, did you try adjusting concurrencyLevel accordingly? The stripped locks are maintained in a kind of hash map and the number of segments is controlled by concurrencyLevel. The default number of segments is controlled by the concurrency level which by default is 32. Try using higher values than that.