[FELIX-5024] "waiting to lock" message serializes "null" when there is no owner thread

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: threaddump-1.0.0
• Fix Version/s: threaddump-1.0.2
• Component/s: Thread Dumper
• Assignee: Unassigned
• Reporter: Simone Tripodi
• Created: 02/Sep/15 08:23
• Updated: 02/Sep/15 09:55

Description

It happen that the waiting to lock message renders a null string when there is no owner thread, it must be removed

"mythread-323" prio=5 tid=0x143 nid=0xffffffff timed_waiting
   java.lang.Thread.State: TIMED_WAITING
        at sun.misc.Unsafe.park(Native Method)
        - waiting to lock <0x406249f1> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) owned by "null" tid=0x-1
        at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
        at org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:389)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.idleJobPoll(QueuedThreadPool.java:531)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.access$700(QueuedThreadPool.java:47)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:590)
        at java.lang.Thread.run(Thread.java:722)