JBoss server threads should have useful names --------------------------------------------- Key: JBAS-2719 URL: http://jira.jboss.com/jira/browse/JBAS-2719 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public(Everyone can see) Affects Versions: JBossAS-4.0.3 Final Reporter: Elias Ross Assigned To: Elias Ross Attachments: timer-use.txt Most threads do have assigned names. However, here is a list of thread dumps where they don't appear: "Thread-3" daemon prio=1 tid=0x9e658538 nid=0x7f9b waiting on condition [9de16000..9de16878] at java.lang.Thread.sleep(Native Method) at org.jboss.console.plugins.AOPLister$1.run(AOPLister.java:869) at java.lang.Thread.run(Thread.java:534) "Thread-10" daemon prio=1 tid=0x080ce940 nid=0x7f9b in Object.wait() [9c45a000..9c45a878] at java.lang.Object.wait(Native Method) - waiting on <0xa5fd77d0> (a org.jboss.mx.util.RunnableScheduler) at org.jboss.mx.util.RunnableScheduler.waitOutstanding(RunnableScheduler.java:202) - locked <0xa5fd77d0> (a org.jboss.mx.util.RunnableScheduler) at org.jboss.mx.util.RunnableScheduler.run(RunnableScheduler.java:96) at java.lang.Thread.run(Thread.java:534) There are also a few created java.util.Timer threads, with no name, but these may belong to my own application. I'm attaching a "grep" for this class for reference. It's useful to be able to know which system component a JBoss thread originates from. This would be a separate documentation step.