Deadlock

本文通过一个简单的Java实例,详细解释了死锁的概念、形成原因以及如何通过同步方法来避免死锁的发生。重点阐述了死锁中线程间的相互等待问题,以及在多线程环境下同步资源管理的重要性。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

Deadlock

Deadlock describes a situation where two or more threads are blocked forever, waiting for each other. Here's an example.

Alphonse and Gaston are friends, and great believers in courtesy. A strict rule of courtesy is that when you bow to a friend, you must remain bowed until your friend has a chance to return the bow. Unfortunately, this rule does not account for the possibility that two friends might bow to each other at the same time. This example application, Deadlock, models this possibility:

public class Deadlock {
    static class Friend {
        private final String name;
        public Friend(String name) {
            this.name = name;
        }
        public String getName() {
            return this.name;
        }
        public synchronized void bow(Friend bower) {
            System.out.format("%s: %s"
                + "  has bowed to me!%n", 
                this.name, bower.getName());
            bower.bowBack(this);
        }
        public synchronized void bowBack(Friend bower) {
            System.out.format("%s: %s"
                + " has bowed back to me!%n",
                this.name, bower.getName());
        }
    }

    public static void main(String[] args) {
        final Friend alphonse =
            new Friend("Alphonse");
        final Friend gaston =
            new Friend("Gaston");
        new Thread(new Runnable() {
            public void run() { alphonse.bow(gaston); }
        }).start();
        new Thread(new Runnable() {
            public void run() { gaston.bow(alphonse); }
        }).start();
    }
}

When  Deadlock runs, it's extremely likely that both threads will block when they attempt to invoke  bowBack. Neither block will ever end, because each thread is waiting for the other to exit  bow.

Synchronized (instance) methods lock on the object, NOT on the class.

alphonse.bow grabs the lock on alphonse and gaston.bow grabs the lock on gaston. When the 'alphonse' thread is in bow, it tries to grab the lock on 'gaston' at bower.bowBack. Likewise, 'gaston' tries to grab the lock on 'alphonse'.

Edit for clarity (I hope):

Let's call the two threads Thread1 and Thread2.

Thread1 runs alphonse.bow(gaston), where it grabs the lock on the alphonse object while Thread2 runs gaston.bow(alphonse) and grabs the lock on the gaston object.

In Thread1, when it attempts to run bower.bowBack(this), where bower = gaston, the thread needs to first acquire the lock on gaston.

While this is going on, Thread2 tries to do the same thing, with bower = alphonse. Thread1 has a lock that Thread2 needs and vice-versa, which is why the deadlock occurs.

As an aside, a deadlock need not always occur. If Thread1 can start and finish before Thread2 has a chance to do so (e.g. if something hangs the main thread after Thread1 has started but before Thread2 is created/started), then no deadlock will occur.

原因:it is not possible for two invocations of synchronized methods on the same object to interleave.  
基于Spring Boot搭建的一个多功能在线学习系统的实现细节。系统分为管理员和用户两个主要模块。管理员负责视频、文件和文章资料的管理以及系统运营维护;用户则可以进行视频播放、资料下载、参与学习论坛并享受个性化学习服务。文中重点探讨了文件下载的安全性和性能优化(如使用Resource对象避免内存溢出),积分排行榜的高效实现(采用Redis Sorted Set结构),敏感词过滤机制(利用DFA算法构建内存过滤树)以及视频播放的浏览器兼容性解决方案(通过FFmpeg调整MOOV原子位置)。此外,还提到了权限管理方面自定义动态加载器的应用,提高了系统的灵活性和易用性。 适合人群:对Spring Boot有一定了解,希望深入理解其实际应用的技术人员,尤其是从事在线教育平台开发的相关从业者。 使用场景及目标:适用于需要快速搭建稳定高效的在线学习平台的企业或团队。目标在于提供一套完整的解决方案,涵盖从资源管理到用户体验优化等多个方面,帮助开发者更好地理解和掌握Spring Boot框架的实际运用技巧。 其他说明:文中不仅提供了具体的代码示例和技术思路,还分享了许多实践经验教训,对于提高项目质量有着重要的指导意义。同时强调了安全性、性能优化等方面的重要性,确保系统能够应对大规模用户的并发访问需求。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值