blocks|key|2248795|text|获得线程转储的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2248796|在Linux/UNIX上，ctrl中断(Windows)或ctrl-\，可能是ctrl-4和kill+-3|unordered-list-item|offset|length|style|CODE|2248797|jstack和您的进程id+(使用jps)|2248798|jconsole或visualvm|2248799|几乎任何调试器|2248800|J2SE+5.0中的主要新线程特性(2004年发布，服务寿命结束)：|2248801|java.util.concurrent|2248802|新的Java内存模型。|2248803|entityMap^0|0|1A|7|0|0|6|H|3|0|0|8|9|8|0|0|0|0|K|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@$E|Y|F|Z|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|10|8|@$E|11|F|12|G|H]|$E|13|F|14|G|H]]|9|@]|A|$]]|$1|K|3|L|5|D|7|15|8|@$E|16|F|17|G|H]|$E|18|F|19|G|H]]|9|@]|A|$]]|$1|M|3|N|5|D|7|1A|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1B|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1C|8|@$E|1D|F|1E|G|H]]|9|@]|A|$]]|$1|S|3|T|5|D|7|1F|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|V|$]]

Way of obtaining thread dumps:

<ul>
<li>ctrl-break (Windows) or ctrl-\, possibly ctrl-4 and <code>kill -3</code> on Linux/UNIX</li>
<li><code>jstack</code> and your process id (use <code>jps</code>)</li>
<li><code>jconsole</code> or <code>visualvm</code></li>
<li>just about any debugger</li>
</ul>

Major new threading features in J2SE 5.0 (released 2004, in End Of Service Life Period):

<ul>
<li><code>java.util.concurrent</code></li>
<li>New Java Memory Model.</li>
</ul>

blocks|key|723262|text|在进程id上使用杀害-3|type|unstyled|depth|inlineStyleRanges|entityRanges|data|723263|这将将线程转储和线程争用的概述打印到控制台。|723264|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

use kill -3 on the process id

this will print out to the console a thread dump and an overview of thread contention

blocks|key|893760|text|在您的程序中，ThreadMXBean类有一个方法ThreadMXBean以及用于查询当前线程堆栈跟踪的方法。在Windows中，执行Ctrl%2BBreak将给出堆栈跟踪列表，并指示死锁线程。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|893761|除了对Java内存模型进行一些调整以清理一些并发“漏洞”之外，Java+5中最重要的特性是它向程序员公开了比较集(CAS)操作。然后，在此基础上，在平台中提供了大量并发实用程序。确实有很多东西，但它们包括：|893762|并发集合|unordered-list-item|893763|执行程序，它有效地允许您实现诸如线程池之类的东西。|893764|其他常见的并发结构(队列、锁、屏障)|893765|原子变量|893766|您可能对我在许多Java+5并发特性上编写的教程感兴趣。|893767|entityMap|0|LINK|mutability|MUTABLE|url|http://www.javamex.com/tutorials/profiling/profiling_java5_threads_howto.shtml|1|2|http://www.javamex.com/tutorials/synchronization_concurrency_1.shtml^0|7|C|0|P|C|1|0|0|0|0|0|0|8|A|2|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]|$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|19|8|@]|9|@]|C|$]]|$1|I|3|J|5|H|7|1A|8|@]|9|@]|C|$]]|$1|K|3|L|5|H|7|1B|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|1C|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1D|8|@]|9|@$A|1E|B|1F|1|1G]]|C|$]]|$1|Q|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]|Y|$5|T|U|V|C|$W|X]]|Z|$5|T|U|V|C|$W|10]]]]

From within your program, the <a href="http://www.javamex.com/tutorials/profiling/profiling_java5_threads_howto.shtml" rel="nofollow noreferrer">ThreadMXBean</a> class has a method findMonitorDeadlockedThreads(), as well as methods for querying the current stack traces of threads. From the console in Windows, doing Ctrl+Break gives you a list of stack traces and indicates deadlocked threads.

As well as some tweaks to the Java memory model that tidy up some concurrency "loopholes", the most significant feature underlyingly in Java 5 is that it exposes Compare-And-Set (CAS) operations to the programmer. Then, on the back of this, a whole raft of concurrency utilities are provided in the platform. There's really a whole host of stuff, but they include:

<ul>
<li>concurrent collections</li>
<li>executors, which effectively allow you to implement things such as thread pools</li>
<li>other common concurrency constructs (queues, latches, barriers)</li>
<li>atomic variables</li>
</ul>

You may be interested in some tutorials I've written on many of the <a href="http://www.javamex.com/tutorials/synchronization_concurrency_1.shtml" rel="nofollow noreferrer">Java 5 concurrency features</a>.

blocks|key|723374|text|如果您想了解Java5中的新并发特性，可能比获得Brian+(Brian和一些共同设计的Java5并发库)的Java并发在实践中的应用副本要糟糕得多。它既具有很高的可读性和权威性，又结合了实例和理论。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|723375|新并发实用程序执行摘要如下：|723376|任务调度框架-执行器框架是根据一组执行策略对异步任务的调用、调度、执行和控制进行标准化的框架。提供的实现允许在提交线程、单个后台线程(如Swing中的事件)、新创建的线程或线程池中执行任务，开发人员可以创建支持任意执行策略的执行器。内建实现提供了队列长度限制和饱和策略等可配置策略，可以通过防止资源消耗来提高应用程序的稳定性。|unordered-list-item|723377|并发集合-添加了几个新的集合类，包括新的队列和BlockingQueue接口，以及地图、列表和队列的高性能并发实现。|723378|原子变量-用于原子操作单变量(原始类型或引用)的类，提供高性能的原子算法和比较和集合方法。java.util.concurrent.atomic中的原子变量实现提供了比使用同步(在大多数平台上)更高的性能，使得它们对于实现高性能并发算法以及方便地实现计数器和序列号生成器非常有用。|723379|同步器-一般用途的同步类，包括信号量、互斥量、屏障、锁存器和交换器，它们有助于线程之间的协调。|723380|锁-虽然锁定是通过同步关键字内置到Java语言中的，但是内置监视器锁有许多不方便的限制。java.util.concurrent.locks包提供了与同步具有相同内存语义的高性能锁实现，但它还支持在尝试获取锁时指定超时、每个锁多个条件变量、非词汇作用域锁以及支持中断等待获取锁的线程。|723381|纳秒-粒度计时-+System.nanoTime方法允许访问纳秒粒度时间源，用于进行相对时间测量，而接受超时的方法(如BlockingQueue.offer、BlockingQueue.poll、Lock.tryLock、Condition.await和Thread.sleep)可以以纳秒为单位获取超时值。System.nanoTime的实际精度与平台有关.|723382|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0321349601|1|http://java.sun.com/j2se/1.5.0/docs/guide/concurrency/overview.html^0|1I|D|0|0|0|B|1|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|F|3|G|5|H|7|1A|8|@]|9|@]|C|$]]|$1|I|3|J|5|H|7|1B|8|@]|9|@]|C|$]]|$1|K|3|L|5|H|7|1C|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|1D|8|@]|9|@]|C|$]]|$1|O|3|P|5|H|7|1E|8|@]|9|@]|C|$]]|$1|Q|3|R|5|H|7|1F|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]]]

If you want to learn about the new concurrent features in Java 5 you could do a lot worse than getting a copy of <a href="https://rads.stackoverflow.com/amzn/click/com/0321349601" rel="nofollow noreferrer" rel="nofollow noreferrer" title="Java Concurrency in Practice">Java Concurrency in Practice</a> by Brian Goetz (Brian Goetz and a number of the coauthors designed the Java 5 concurrency libraries). It is both highly readable and authoritative , and combining practical examples and theory.

The <a href="http://java.sun.com/j2se/1.5.0/docs/guide/concurrency/overview.html" rel="nofollow noreferrer" title="Concurrency Utilities Overview">executive summary of the new concurrent utilities</a> is as follows:

<ul>
<li>Task Scheduling Framework - The Executor framework is a framework for standardizing invocation, scheduling, execution, and control of asynchronous tasks according to a set of execution policies. Implementations are provided that allow tasks to be executed within the submitting thread, in a single background thread (as with events in Swing), in a newly created thread, or in a thread pool, and developers can create of Executor supporting arbitrary execution policies. The built-in implementations offer configurable policies such as queue length limits and saturation policy which can improve the stability of applications by preventing runaway resource consumption.</li>
<li>Concurrent Collections - Several new Collections classes have been added, including the new Queue and BlockingQueue interfaces, and high-performance, concurrent implementations of Map, List, and Queue.</li>
<li>Atomic Variables - Classes for atomically manipulating single variables (primitive types or references), providing high-performance atomic arithmetic and compare-and-set methods. The atomic variable implementations in java.util.concurrent.atomic offer higher performance than would be available by using synchronization (on most platforms), making them useful for implementing high-performance concurrent algorithms as well as conveniently implementing counters and sequence number generators.</li>
<li>Synchronizers - General purpose synchronization classes, including semaphores, mutexes, barriers, latches, and exchangers, which facilitate coordination between threads.</li>
<li>Locks - While locking is built into the Java language via the synchronized keyword, there are a number of inconvenient limitations to built-in monitor locks. The java.util.concurrent.locks package provides a high-performance lock implementation with the same memory semantics as synchronization, but which also supports specifying a timeout when attempting to acquire a lock, multiple condition variables per lock, non-lexically scoped locks, and support for interrupting threads which are waiting to acquire a lock.</li>
<li>Nanosecond-granularity timing - The System.nanoTime method enables access to a nanosecond-granularity time source for making relative time measurements, and methods which accept timeouts (such as the BlockingQueue.offer, BlockingQueue.poll, Lock.tryLock, Condition.await, and Thread.sleep) can take timeout values in nanoseconds. The actual precision of System.nanoTime is platform-dependent. </li>
</ul>

Can somebody tell me how I can find out "how many threads are in deadlock condition" in a Java multi-threading application? What is the way to find out the list of deadlocked threads?

I heard about Thread Dump and Stack Traces, but I don't know how to implement it.

<ul>
<li>I also want to know what new features have been introduced in Java 5 for Threading?</li>
</ul>

Please let me know with your comments and suggestions.

Dead Lock Thread Check

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

有人能告诉我如何在Java多线程应用程序中找到“多少线程处于死锁状态”吗？找到死锁线程列表的方法是什么？我听说过线程转储和堆栈跟踪，但我不知道如何实现它。我还想知道Java 5中为线程化引入了哪些新特性？请让我知道你的意见和建议。

问死锁线程检查
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问死锁线程检查EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问死锁线程检查
EN