Show Table of Contents
16.3. Configure Lock Striping (Library Mode)
Lock striping is disabled by default in Red Hat JBoss Data Grid. Configure lock striping in JBoss Data Grid's Library mode using the
striping parameter as demonstrated in the following procedure.
Procedure 16.1. Configure Lock Striping (Library Mode)
<local-cache>
<locking concurrency-level="${VALUE}"
isolation="${LEVEL}"
acquire-timeout="${TIME}"
striping="${TRUE/FALSE}"
write-skew="${TRUE/FALSE}" />
</local-cache>- The
concurrency-levelis used to specify the size of the shared lock collection use when lock striping is enabled. - The
isolationparameter specifies the cache's isolation level. Valid isolation levels areREAD_COMMITTEDandREPEATABLE_READ. - The
acquire-timeoutparameter specifies time (in milliseconds) after which a lock acquisition attempt times out. - The
stripingparameter specifies whether a pool of shared locks are maintained for all entries that require locks. If set toFALSE, locks are created for each entry in the cache. If set toTRUE, lock striping is enabled and shared locks are used as required from the pool. - The
write-skewcheck determines if a modification to the entry from a different transaction should roll back the transaction. Write skew set to true requiresisolation_levelset toREPEATABLE_READ. The default value forwrite-skewandisolation_levelareFALSEandREAD_COMMITTEDrespectively. Thewrite-skewparameter can be only used withOPTIMISTICtransactions and it requires entry versioning to be enabled, withSIMPLEversioning scheme.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.