Using locking

Locks have life cycles and different types of locks are compatible with others in various ways. Locks must be handled in the correct order to avoid deadlock scenarios.

Configuring and implementing locking in Java applications
You can define an optimistic, a pessimistic, or no locking strategy on each BackingMap in the WebSphere® eXtreme Scale configuration.
Example: flush method lock ordering
Invoking the flush method on the ObjectMap interface before a commit can introduce additional lock ordering considerations. The flush method is typically used to force changes that are made to the map out to the backend through the Loader plug-in.
Implementing exception handling in locking scenarios for Java applications
To prevent locks from being held for excessive amounts of time when a LockTimeoutException exception or a LockDeadlockException exception occurs, your application must catch unexpected exceptions and call the rollback method when an unexpected event occurs.
Map entry locks with query and indexes
The eXtreme Scale Query APIs and the MapRangeIndex indexing plug-in interact with locks. You can increase concurrency and decrease deadlocks when you are using the pessimistic locking strategy for maps.
Java examples for transaction isolation
Transaction isolation defines how the changes that are made by one operation become visible to other concurrent operations. You can use the following examples to define the transaction isolation level in your Java application.
Optimistic collision exception
You can receive an OptimisticCollisionException directly, or receive it with an ObjectGridException.
Running parallel business logic on the data grid (DataGrid API)
The DataGrid API provides a simple programming interface to run business logic over all or a subset of the data grid in parallel with where the data is located.

Parent topic: Programming for transactions in Java applications

Last updated: 2021-03-29