blocks|key|985551|text|我虔诚地命名我的线程(比如使用线程(可运行，字符串)+)，否则它们最终会有一个通用的、有些无用的名称。转储线程将突出显示正在运行的内容以及(因此)创建它们的内容。这并不能解决第三方线程的创建，我很感激。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|985552|编辑:+JavaSpecialist时事通讯最近(2015年2月)通过使用安全管理器解决了这个问题。请参阅关于更多细节，请到这里|985553|更多:关于使用JavaSpecialist技术的几个细节:+SecurityManager+API包括在线程创建者的线程上调用的"checkAccess(newThreadBeingCreated)“。新线程已经初始化了它的“名称”。因此，在该方法中，您可以访问线程创建者的线程和新线程，并且可以记录/打印等等。当我尝试此方法时，被监视的代码将开始抛出访问保护异常；我通过在AccessController.doPriviledged(新的PrivilegedAction()+{.}，其中run()方法调用被监视的代码)下调用它来修正这个问题。|985554|entityMap|0|LINK|mutability|MUTABLE|url|http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Thread.html#Thread%2528java.lang.Runnable,%2520java.lang.String%2529|1|http://www.javaspecialists.eu/archive/Issue226.html^0|F|B|0|0|1H|B|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

I religiously name my threads (using <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Thread.html#Thread%28java.lang.Runnable,%20java.lang.String%29" rel="nofollow noreferrer">Thread(Runnable, String)</a>, say), otherwise they end up with a generic and somewhat useless name. Dumping the threads will highlight what's running and (thus) what's created them. This doesn't solve 3rd party thread creation, I appreciate.

EDIT: The JavaSpecialist newsletter addressed this issue recently (Feb 2015) by using a security manager. See <a href="http://www.javaspecialists.eu/archive/Issue226.html" rel="nofollow noreferrer">here for more details</a>

MORE: A couple of details for using the JavaSpecialist technique: The SecurityManager API includes "checkAccess(newThreadBeingCreated)" that is called on the thread creator's thread. The new thread already has its "name" initialized. So in that method, you have access to both the thread creator's thread, and the new one, and can log / print etc. When I tried this the code being monitored started throwing access protection exceptions; I fixed that by calling it under a AccessController.doPriviledged(new PrivilegedAction() { ... } where the run() method called the code being monitored.

blocks|key|908550|text|不幸的是，在Eclipse中，我看到了所有阻塞线程，但是它们的堆栈跟踪只反映它们的内部状态，而且(显然)没有透露它们创建位置的任何信息。此外，通过查看对象内部(使用变量视图)，我无法获得任何进一步的提示。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|908551|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Unfortunately it doesn't. Within Eclipse I see all the blocking threads, but their stack traces only reflect their internal state and (apparently) disclose no information about the location of their creation. Also from a look inside the object (using the Variables view) I was unable to elicit any further hints.

blocks|key|2434331|text|在调试Eclipse应用程序时，可以通过单击调试视图中的org.eclipse.equinox.launcher.Main字段来停止所有线程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2434332|然后，对于每个线程，您可以看到堆栈跟踪并进入thred方法。|2434333|有时这会有帮助，有时却没有帮助。|2434334|正如Brian所说，命名线程是一种很好的做法，因为这是很容易识别“是谁创建了它们”的唯一方法。|2434335|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

When debuging your Eclipse application, you can stop all thread by clicking org.eclipse.equinox.launcher.Main field in the debug view.

Then from there, for each thread you can see the stack trace and goes up to the thred run method.

Sometimes this can help and sometimes not.

As Brian said, it a good practice to name threads because it's the only way to easily identify "who created them"

blocks|key|985595|text|好吧，我自己解决了这个问题:我把一个断点|type|unstyled|depth|inlineStyleRanges|entityRanges|data|985596|Thread.start()+|code-block|syntax|javascript|985597|手动完成每一次调用。通过这种方式，我很快发现Class.forName()初始化了大量静态代码，而这些代码反过来又创建了这些神秘的线程。|985598|虽然我能够解决我的问题，但我仍然认为，更普遍的任务仍然没有得到解决。|985599|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Okay, I was able to solve (sort of) the problem on my own: I put a breakpoint into 

<pre><code>Thread.start() 
</code></pre>

and manually stepped through each invocation. This way I found out pretty quickly that Class.forName() initialized lot of static code which in return created these mysterious threads. 

While I was able to solve my problem I still think the more general task still remains unaddressed.

blocks|key|2434368|text|为了进行本地调试，可以尽早将调试器附加到Java应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2434369|在的末尾设置一个不挂起的断点，它将计算并记录如下：|offset|length|style|BOLD|2434370|"**"+%2B+getName()+%2B+"**\n"+%2B+Arrays.toString(Thread.currentThread().getStackTrace())|code-block|syntax|javascript|2434371|这将输出线程名和线程如何创建(堆栈跟踪)，您只需扫描即可。|2434372|entityMap^0|0|1|D|H|5|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

For local debugging purposes, one can attach a debugger to a Java application as early as possible.

Set a non-suspending breakpoint at the end of <code>java.lang.Thread#init(java.lang.ThreadGroup, java.lang.Runnable, java.lang.String, long, java.security.AccessControlContext, boolean)</code> that will Evaluate and log the following:

<pre><code>"**" + getName() + "**\n" + Arrays.toString(Thread.currentThread().getStackTrace())
</code></pre>

This will out the thread name and how the thread is created (stacktrace) that one can just scan through.

How can I find out who created a Thread in Java? 

Imagine the following: You use ~30 third party JARs in a complex plugin environment. You start it up, run lots of code, do some calculations and finally call shutdown(). 

This life-cycle usually works fine, except that on every run some (non-daemonic) threads remain dangling. This would be no problem if every shutdown was the last shutdown, I could simply run System.exit() in that case. However, this cycle may run several times and it's producing more garbage every pass.

So, what should I do? I see the threads in Eclipse's Debug View. I see their stack traces, but they don't contain any hint about their origin. No creator's stack trace, no distinguishable class name, nothing. 

Does anyone have an idea how to address this problem?

Detect Who Created a Thread (w. Eclipse)

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我如何找出谁在Java中创建了线程？假设以下情况:在一个复杂的插件环境中使用~30 第三方JAR。启动它，运行大量的代码，做一些计算，最后调用start ()。这个生命周期通常可以正常工作，但每次运行时，一些(非守护进程)线程仍然处于悬空状态。如果每次关闭都是最后一次关闭，那么这就没有问题了，在这种情况下，我可以简单地...

问检测谁创建了线程(w. Eclipse)
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问检测谁创建了线程(w. Eclipse)EN