[
https://issues.apache.org/jira/browse/FELIX-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated FELIX-5024:
----------------------------------
Attachment: FELIX-5024.patch
Proposed patch fixes the issue simply by checking the owner ID inside the
message format, it skips the owner details rendering if there is no owner
> "waiting to lock" message serializes "null" when there is no owner thread
> -------------------------------------------------------------------------
>
> Key: FELIX-5024
> URL: https://issues.apache.org/jira/browse/FELIX-5024
> Project: Felix
> Issue Type: Bug
> Components: Thread Dumper
> Affects Versions: threaddump-1.0.0
> Reporter: Simone Tripodi
> Fix For: threaddump-1.0.2
>
> Attachments: FELIX-5024.patch
>
>
> It happen that the {{waiting to lock}} message renders a _null_ string when
> there is no owner thread, it must be removed
> {noformat}
> "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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
