Enabling Transaction Locks in Spring Data JPA

Transaction locks in Spring Data JPA can help manage concurrent data access. It can ensure the data consistency. By controlling how transactions acquire the locks on the database rows or tables, we can prevent issues such as lost updates and ensure that the application maintains data integrity. This article will guide you through enabling the transaction locks using Spring Data JPA with practical examples and explanations.

Transaction locks are crucial for managing concurrent access to the data in the database. It ensures data integrity and consistency when multiple transactions interact with the same data. In Spring Data JPA, two primary types of locks are used: Pessimistic Locking and Optimistic Locking. Each approach has its own use cases, benefits, and drawbacks.

1. Pessimistic Locking

Pessimistic Locking assumes that conflicts will occur and locks the data to prevent the other transactions from accessing it concurrently. This type of locking can be useful in scenarios where you can expect high contention for the same data or when transactions involve complex operations that should not be implemented.

How It Works

1. Acquire Lock:

• When the transaction reads a record with the pessimistic lock, the database acquires the lock on that record.
• The lock can be of the different types, such as PESSIMISTIC_READ (prevents other transactions from writing) or PESSIMISTIC_WRITE (prevents other transactions from reading or writing).

2. Block Other Transactions

• Other transactions trying to access the same record will be blocked until the lock can be released. This prevents data inconsistency caused by the concurrent modifications.

3. Release Lock

• The lock is held for the duration of the transaction and it can be automatically released when the transaction commits or rolls back.

Implementation in Spring Data JPA

In Spring Data JPA, we can implement the pessimistic locking using @Lock annotation with LockModeType.PESSIMISTIC_WRITE or LockModeType.PESSIMISTIC_READ on the repository method.

Example:

import org.springframework.data.jpa.repository.JpaRepository;
import org.springframework.data.jpa.repository.Lock;
import org.springframework.data.jpa.repository.Query;
import org.springframework.stereotype.Repository;

import javax.persistence.LockModeType;
import java.util.Optional;

@Repository
public interface ProductRepository extends JpaRepository<Product, Long> {

 @Lock(LockModeType.PESSIMISTIC_WRITE)
 @Query("SELECT p FROM Product p WHERE p.id = :id")
 Optional<Product> findByIdForUpdate(Long id);
}

Explanation:

• @Lock(LockModeType.PESSIMISTIC_WRITE): It can acquires the write lock on the record when it is read.
• findByIdForUpdate(Long id): This method can retrieves the product by its ID and locks it for writing.

Use Case

Support the two users are trying to update the price of the same product simultaneously. Pessimistic locking will ensure that only one user can be modify the record at the time preventing data inconsistency.

2. Optimistic Locking

Optimistic Locking assumes that conflicts are rare and allows the concurrent transactions to proceed without locking the data. It uses the version field to detect the conflicts and ensure that updates do not overwrite the each other.

How It Works

1. Version Field: Each entity has the version field and typically annotated with @Version. This field can be used to track changes to the entity.
2. Check Version: When the transaction updates the record, it includes the current version of the record. The database can checks if the version in the transaction matches the version in the database. If they can match then the update proceeds.
3. Detect Conflicts: If another transaction has updated the record and changed the version, the current transaction with fail with an OptimisticLockException. It indicates the conflict that needs to be resolved.
4. Handle Exceptions: The application must handle the OptimisticLockException by retrying the transaction or informing the user of the conflict.

Implementation in Spring Data JPA

In Spring Data JPA, we can optimistic locking is implemented using the @Version annotation on the field in the entity class.

Example:

import jakarta.persistence.*;

@Entity
public class Product {

 @Id
 @GeneratedValue(strategy = GenerationType.IDENTITY)
 private Long id;

 private String name;
 private Double price;

 @Version
 private Long version;
}

Explanation:

• @Version: It makes the version field used for the optimistic locking.
• The version field can be automatically updated by the Hibernate on the each update.

Use Case

If two users try to update the price of the same product simultaneously, optimistic locking will be detect the conflict and the prevent one of the updates from being applied, ensuring that the most recent version of the data is used.

Implementation of Enabling Transaction Locks in Spring Data JPA

Step 1: Create a New Spring Boot project

Create a new Spring Boot Project using IntelliJ Idea. Choose the below options:

• Name: transaction-locks-demo
• Language: Java
• Type: Maven
• Packaging: Jar

Click on the Next button.

Step 2: Add the dependencies

Add the following dependencies into the Spring Boot project.

Step 3: Project Structure

Once created the project, the file structure looks like the below image.

Step 4: Configure the Application Properties

Open the application.properties file and add the following configuration of MySQL into the Spring Boot Project.

spring.application.name=transaction-locks-demo

spring.datasource.url=jdbc:mysql://localhost:3306/transaction_locks
spring.datasource.username=root
spring.datasource.password=mypassword
spring.jpa.hibernate.ddl-auto=update
spring.jpa.show-sql=true

Step 5: Create the Product Entity

The Product entity class can defines the entity with the both pessimistic and optimistic locking.

Step 6: Create the ProductRepositoy Interface

This repository interface for accessing the Product entities with methods for the pessimistic locking.

Step 7: Create the ProductService Class

This ProductService layer class with methods to demonstrates both the pessimistic and optimistic locking.

Step 8: Create the ProductController Class

Create the controller class named as ProductController, it will handle the HTTP requests to update the product price using the both pessimistic and optimistic locking mechanisms.

Step 9: Main Class

No changes are required in the main class.

pom.xml file:

Step 10: Run the application

Once completed the project, it will start and run at port 8080.

Step 11: Testing the Application

1. Save the Products

POST http://localhost:8080/products

Output:

2. Pessimistic Lock Endpoint

PUT http://localhost:8080/products/pessimistic/1?newPrice=1300.0

Output:

This request will update the price of the product with id 1 to 1300.0 using the pessimistic locking. It ensures that the product record is locked for the duration of the transaction to prevent the concurrent modifications.

3. Optimistic Lock Endpoint

PUT http://localhost:8080/products/optimistic/1?newPrice=1400.0

Output:

This request will update the price of product with id 1 to 1400.0 using the optimistic locking. It uses the version field to detect concurrent the updates and handle conflicts.