Rrd Queueing Threads don't identify themselves
Description
Environment
Acceptance / Success Criteria
Lucidchart Diagrams
Activity
Seth Leger (community account) May 21, 2010 at 4:46 PM
I combed through the code and added names to several threads including the QueuingRrdStrategy threads. Marking as fixed.
Seth Leger (community account) May 21, 2010 at 11:24 AM
This would be nice... having the thread names cleaned up definitely helps people debug problems.
Here are some threads on my system without names that we can probably label:
"Thread-20" prio=10 tid=0x9657a000 nid=0x294 waiting on condition [0x95e08000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at org.opennms.netmgt.provision.MapProvisioningAdapter$MapSyncExecutor.run(MapProvisioningAdapter.java:264)
at java.lang.Thread.run(Thread.java:619)
"default" prio=10 tid=0x9656b800 nid=0x282 in Object.wait() [0x96225000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at org.opennms.netmgt.notifd.DefaultQueueHandler.run(DefaultQueueHandler.java:150)
locked <0xa812c260> (a org.opennms.netmgt.notifd.DefaultQueueHandler)
at java.lang.Thread.run(Thread.java:619)
"ConsumerThread" prio=10 tid=0x999a4400 nid=0x143 waiting on condition [0x98bad000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at org.opennms.netmgt.rrd.tcp.QueuingTcpRrdStrategy$ConsumerThread.run(QueuingTcpRrdStrategy.java:112)
When you take a thread dump for the java process running opennms, the threads associated with QueuingRrdStrategy all show up as "Thread-${NUM}". It would be nice if they had their own name like "QueueingRrdThread-${NUM}".