Managing access to shared resources is important in concurrent programming to ensure data consistency. Traditional synchronized keyword lacks flexibility for complex scenarios like fairness, acquire lock immediately, wait for a specific time to acquire lock, etc. Lock, ReadWriteLock, and StampedLock APIs are introduced in Java 1.5 to addresses these limitation and provides great control to developers to handle shared resources access. They are part of java.util.concurrent package.
Lock API
Lock API is an interface and provides below methods to handle thread synchronization.
- void lock() It is used to acquire the lock. If the lock is not available, the thread will be blocked until the lock is acquired.
- void lockInterruptibly() It is same as lock(), but this thread can be interrupted.
- boolean tryLock() It returns true if the lock is acquired; otherwise, false. The thread will not be blocked if the lock is not granted.
- boolean tryLock(long timeout, TimeUnit unit) It is same as tryLock() but waits for a specified amount of time only.
- void unlock()Releases the lock.
- Condition newCondition() Provides the ability for a thread to wait for some condition to occur while executing the critical part.
ReentrantLock
- ReentrantLock class implements the Lock interface.?
- A reentrant lock allows a thread to acquire a lock multiple times and release it multiple times.
- If you want fairness policy, use parameterized constructor of ReentrantLock.
- If fairness is enabled, It makes sure that the longest waiting thread is given access to the lock.
- Use finally block to release the lock to avoid deadlock situation.
ReentrantLock lock = new ReentrantLock(true); //fair lock public void methodExecution() { lock.lock(); try { // Critical section here } finally { lock.unlock(); } }
ReadWriteLock API
ReadWriteLock API is an interface and maintains a pair of locks to maintain read and write scenarios. The read lock can be held simultaneously by multiple threads if there are no writers. The write lock is exclusive.
- Lock readLock() - Returns the lock used for reading.
- Lock writeLock() - Returns the lock used for writing.
Key Rules
- If you have a read lock, you can't acquire a write lock.
- If you have a write lock, you can't acquire a read lock in any other thread.
- If you have a write lock, you can acquire another write lock in the same thread.
- A write lock is allowed when no other read or write lock is active.
- While waiting for a write lock, no new read locks from other threads are allowed.
ReentrantReadWriteLock
- ReentrantReadWriteLock class implements the ReadWriteLock interface.
- Useful if we have more read compare to write.
Example: In micro-service communication, assume Service B expects a JWT from Service A. JWT is generated by Service A and can be cacheable for couple of minutes. In this scenarios ReentrantReadWriteLock will be more useful. We can renew the token if it is expired or about to expire. I am not acquiring read lock here to avoid read starvation.
ReentrantLock lock = new ReentrantLock(true); //fair lock public void methodExecution() { lock.lock(); try { // Critical section here } finally { lock.unlock(); } }
StampedLock API
StampedLock was introduced in Java 8 and it is a class. It supports three modes of locking and returns a stamp that is used to release the lock. It allows lock upgradation.
- Read Lock Allows multiple threads to read concurrently.
- Write Lock Returns a lock used for writing.
- Optimistic Read Lock Allows a thread to read without acquiring a traditional read lock, which improves performance as it avoids contention.
- long writeLock() Acquires the exclusive lock, blocking if necessary until available.
- void unlockWrite(long stamp) Releases the write lock.
- long readLock() Acquires the read lock, blocks if a write lock is in progress.
- void unlockRead(long stamp) Releases the read lock.
- long tryOptimisticRead() Returns a stamp that can later be validated, or zero if exclusively locked.
- boolean validate(long stamp) Returns true if the lock has not been exclusively acquired (write lock) since the issuance of the given stamp; otherwise, false.
- long tryConvertToWriteLock(long stamp) Upgrades a read or optimistic lock to a write lock. Blocks until it is available.
Key Points:
- It is not reentrant, meaning a thread holding a lock cannot acquire it again.
- It doesn’t support conditions.
- It doesn’t support fairness.
String jwt = JwtUtil.generateJwt(); ReadWriteLock lock = new ReentrantReadWriteLock(); Lock writeLock = lock.writeLock(); Lock readLock = lock.readLock(); public String getJwt(String key, String value) { if (StringUtils.hasLength(jwt)) { if (JwtUtil.isJwtEligibleToRenew(jwt)) { generateJwt(); } } else { generateJwt(); } return this.jwt; } public void generateJwt() { this.writeLock.lock(); //write lock try { if (JwtUtil.isJwtEligibleToRenew(jwt)) { this.jwt = JwtUtil.generateJwt(); } } finally { this.writeLock.unlock(); //release write lock } }
Optimistic read example. This allows a thread to read without acquiring a traditional read lock, which improves performance as it avoids lock contention. If any write lock acquired after acquiring optimistic read lock time, validate() will return false otherwise it will be true.
public void readAndWrite() { long l = this.stampedLock.readLock(); try { //critical section } finally { this.stampedLock.unlock(l); } long w = this.stampedLock.writeLock(); try { //critical section } finally { this.stampedLock.unlock(w); } }
Happy Coding and Learning !!!
Please drop a comment if you have any question.
The above is the detailed content of Overview of Lock API in java. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The difference between HashMap and Hashtable is mainly reflected in thread safety, null value support and performance. 1. In terms of thread safety, Hashtable is thread-safe, and its methods are mostly synchronous methods, while HashMap does not perform synchronization processing, which is not thread-safe; 2. In terms of null value support, HashMap allows one null key and multiple null values, while Hashtable does not allow null keys or values, otherwise a NullPointerException will be thrown; 3. In terms of performance, HashMap is more efficient because there is no synchronization mechanism, and Hashtable has a low locking performance for each operation. It is recommended to use ConcurrentHashMap instead.

StaticmethodsininterfaceswereintroducedinJava8toallowutilityfunctionswithintheinterfaceitself.BeforeJava8,suchfunctionsrequiredseparatehelperclasses,leadingtodisorganizedcode.Now,staticmethodsprovidethreekeybenefits:1)theyenableutilitymethodsdirectly

The JIT compiler optimizes code through four methods: method inline, hot spot detection and compilation, type speculation and devirtualization, and redundant operation elimination. 1. Method inline reduces call overhead and inserts frequently called small methods directly into the call; 2. Hot spot detection and high-frequency code execution and centrally optimize it to save resources; 3. Type speculation collects runtime type information to achieve devirtualization calls, improving efficiency; 4. Redundant operations eliminate useless calculations and inspections based on operational data deletion, enhancing performance.

Instance initialization blocks are used in Java to run initialization logic when creating objects, which are executed before the constructor. It is suitable for scenarios where multiple constructors share initialization code, complex field initialization, or anonymous class initialization scenarios. Unlike static initialization blocks, it is executed every time it is instantiated, while static initialization blocks only run once when the class is loaded.

Factory mode is used to encapsulate object creation logic, making the code more flexible, easy to maintain, and loosely coupled. The core answer is: by centrally managing object creation logic, hiding implementation details, and supporting the creation of multiple related objects. The specific description is as follows: the factory mode handes object creation to a special factory class or method for processing, avoiding the use of newClass() directly; it is suitable for scenarios where multiple types of related objects are created, creation logic may change, and implementation details need to be hidden; for example, in the payment processor, Stripe, PayPal and other instances are created through factories; its implementation includes the object returned by the factory class based on input parameters, and all objects realize a common interface; common variants include simple factories, factory methods and abstract factories, which are suitable for different complexities.

There are two types of conversion: implicit and explicit. 1. Implicit conversion occurs automatically, such as converting int to double; 2. Explicit conversion requires manual operation, such as using (int)myDouble. A case where type conversion is required includes processing user input, mathematical operations, or passing different types of values ??between functions. Issues that need to be noted are: turning floating-point numbers into integers will truncate the fractional part, turning large types into small types may lead to data loss, and some languages ??do not allow direct conversion of specific types. A proper understanding of language conversion rules helps avoid errors.

Java uses wrapper classes because basic data types cannot directly participate in object-oriented operations, and object forms are often required in actual needs; 1. Collection classes can only store objects, such as Lists use automatic boxing to store numerical values; 2. Generics do not support basic types, and packaging classes must be used as type parameters; 3. Packaging classes can represent null values ??to distinguish unset or missing data; 4. Packaging classes provide practical methods such as string conversion to facilitate data parsing and processing, so in scenarios where these characteristics are needed, packaging classes are indispensable.

InJava,thefinalkeywordpreventsavariable’svaluefrombeingchangedafterassignment,butitsbehaviordiffersforprimitivesandobjectreferences.Forprimitivevariables,finalmakesthevalueconstant,asinfinalintMAX_SPEED=100;wherereassignmentcausesanerror.Forobjectref
