


What are the underlying principles and lock upgrade process of synchronized in Java?
Apr 19, 2025 pm 09:48 PM Deepening Java synchronized
: Low-level mechanism and lock upgrade
synchronized
is an important keyword used for thread synchronization in Java. Its underlying implementation and lock upgrade mechanism are crucial to concurrency performance. This article will explore the operating details of synchronized
and analyze the lock upgrade process in combination with sample code.
The following sample code demonstrates the transition of different lock states:
public static void main(String[] args) throws InterruptedException { // There is a 4-second delay after the Hotspot virtual machine starts before the bias lock is enabled Thread.sleep(5000); Object obj = new Object(); System.out.println("Initial status======================================================= "\n" ClassLayout.parseInstance(obj).toPrintable()); new Thread(() -> { synchronized (obj) { System.out.println(Thread.currentThread().getName() "Get lock is being executed...\n" ClassLayout.parseInstance(obj).toPrintable()); } }, "Thread A").start(); Thread.sleep(1000); new Thread(() -> { synchronized (obj) { System.out.println(Thread.currentThread().getName() "Get lock is being executed...\n" ClassLayout.parseInstance(obj).toPrintable()); } }, "Thread B").start(); // Thread.sleep(5000); System.out.println(Thread.currentThread().getName() ClassLayout.parseInstance(obj).toPrintable()); }
Run this code and observe the output results to see the conversion process of the lock state from lockless to biased lock, lightweight lock, and even heavyweight lock (note: the biased lock has been deprecated by the higher version of JVM).
The synchronized
lock upgrade process is as follows:
- Lockless state: the initial state of the object, the object header contains information such as hash code, GC age, etc.
- Biased locks (deprecated in newer JVM versions): When only one thread accesses a synchronization block, the JVM biases the lock to the thread, and the object header records biased to the thread ID, reducing the overhead of lock acquisition.
- Lightweight lock: When the second thread tries to acquire the lock, if the thread that biases the lock is not executed in the synchronous block, the bias lock is upgraded to a lightweight lock. The lightweight lock acquires the lock through spin attempts, with limited spins, and if it fails, it upgrades to a heavyweight lock.
- Heavyweight lock: thread hangs, operating system scheduling, high overhead, suitable for high competition scenarios.
The output of the sample code will show the transition of the lock state, such as from lock-free to lightweight locks, to possible heavyweight locks. (The bias lock status may not be displayed because the bias lock is deprecated). Analyzing these outputs allows you to have a deeper understanding of the dynamic process of lock upgrade.
In short, understanding the underlying mechanism and lock upgrade process of synchronized
is crucial to mastering Java concurrent programming and performance optimization. Through code practice and result analysis, this knowledge can be learned and applied more effectively.
The above is the detailed content of What are the underlying principles and lock upgrade process of synchronized 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 core method of building social sharing functions in PHP is to dynamically generate sharing links that meet the requirements of each platform. 1. First get the current page or specified URL and article information; 2. Use urlencode to encode the parameters; 3. Splice and generate sharing links according to the protocols of each platform; 4. Display links on the front end for users to click and share; 5. Dynamically generate OG tags on the page to optimize sharing content display; 6. Be sure to escape user input to prevent XSS attacks. This method does not require complex authentication, has low maintenance costs, and is suitable for most content sharing needs.

To realize text error correction and syntax optimization with AI, you need to follow the following steps: 1. Select a suitable AI model or API, such as Baidu, Tencent API or open source NLP library; 2. Call the API through PHP's curl or Guzzle and process the return results; 3. Display error correction information in the application and allow users to choose whether to adopt it; 4. Use php-l and PHP_CodeSniffer for syntax detection and code optimization; 5. Continuously collect feedback and update the model or rules to improve the effect. When choosing AIAPI, focus on evaluating accuracy, response speed, price and support for PHP. Code optimization should follow PSR specifications, use cache reasonably, avoid circular queries, review code regularly, and use X

User voice input is captured and sent to the PHP backend through the MediaRecorder API of the front-end JavaScript; 2. PHP saves the audio as a temporary file and calls STTAPI (such as Google or Baidu voice recognition) to convert it into text; 3. PHP sends the text to an AI service (such as OpenAIGPT) to obtain intelligent reply; 4. PHP then calls TTSAPI (such as Baidu or Google voice synthesis) to convert the reply to a voice file; 5. PHP streams the voice file back to the front-end to play, completing interaction. The entire process is dominated by PHP to ensure seamless connection between all links.

PHP ensures inventory deduction atomicity through database transactions and FORUPDATE row locks to prevent high concurrent overselling; 2. Multi-platform inventory consistency depends on centralized management and event-driven synchronization, combining API/Webhook notifications and message queues to ensure reliable data transmission; 3. The alarm mechanism should set low inventory, zero/negative inventory, unsalable sales, replenishment cycles and abnormal fluctuations strategies in different scenarios, and select DingTalk, SMS or Email Responsible Persons according to the urgency, and the alarm information must be complete and clear to achieve business adaptation and rapid response.

When choosing an AI writing API, you need to examine stability, price, function matching and whether there is a free trial; 2. PHP uses Guzzle to send POST requests and uses json_decode to process the returned JSON data, pay attention to capturing exceptions and error codes; 3. Integrating AI content into the project requires an audit mechanism and supporting personalized customization; 4. Cache, asynchronous queue and current limiting technology can be used to optimize performance to avoid bottlenecks due to high concurrency.

The top ten authoritative cryptocurrency market and data analysis platforms in 2025 are: 1. CoinMarketCap, providing comprehensive market capitalization rankings and basic market data; 2. CoinGecko, providing multi-dimensional project evaluation with independence and trust scores; 3. TradingView, having the most professional K-line charts and technical analysis tools; 4. Binance market, providing the most direct real-time data as the largest exchange; 5. Ouyi market, highlighting key derivative indicators such as position volume and capital rate; 6. Glassnode, focusing on on-chain data such as active addresses and giant whale trends; 7. Messari, providing institutional-level research reports and strict standardized data; 8. CryptoCompa

To enable PHP containers to support automatic construction, the core lies in configuring the continuous integration (CI) process. 1. Use Dockerfile to define the PHP environment, including basic image, extension installation, dependency management and permission settings; 2. Configure CI/CD tools such as GitLabCI, and define the build, test and deployment stages through the .gitlab-ci.yml file to achieve automatic construction, testing and deployment; 3. Integrate test frameworks such as PHPUnit to ensure that tests are automatically run after code changes; 4. Use automated deployment strategies such as Kubernetes to define deployment configuration through the deployment.yaml file; 5. Optimize Dockerfile and adopt multi-stage construction

This article elaborates on two main methods to realize call hold and unhold in Twilio. The preferred option is to leverage Twilio's Conference feature to easily enable call retention and recovery by updating the conference participant resources, and to customize music retention. Another approach is to deal with independent call legs, which requires more complex TwiML logic, passed, and arrived management, but is more cumbersome than meeting mode. The article provides specific code examples and operation steps to help developers efficiently implement Twilio call control.
