TDA 2.4 "find long running threads" broken for java 11

[lukas-cernovsky]

Thread dumps from JDK 11 include cpu= and elapsed= fields in each thread's first line with different value for each dump.
TDA does not detect any threads to be long running. It seems TDA uses also those /value varying/ fields for comparison causing no thread can ever match each other (see my TDA output at the botoom).

Example - folowing two threads are NOT detected as long running. But they have the same call stack.

dump1:
"C2 CompilerThread0" #5 daemon prio=9 os_prio=0 cpu=55652.75ms elapsed=107142.81s tid=0x00007f4b3883d000 nid=0x10854 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
No compile task

dump2:
"C2 CompilerThread0" #5 daemon prio=9 os_prio=0 cpu=55652.76ms elapsed=107145.12s tid=0x00007f4b3883d000 nid=0x10854 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
No compile task

TDA outputs:
Dump No. 2, Dump No. 3
Overall Thread Count 0
Minimum Occurence of threads 2
No threads were found which occured at least 2 times. You should check your dumps for long running threads or adjust the minimum occurence.

[bhargavmodi]

@irockel what is cause of the issue?

[irockel]

@bhargavmodi there were som thread conditions added to the thread info line, like cpu time, these are of course different with every dump and break the long running thread detection, as it matches this line. To fix this, they need to be filtered