There is no such reference in my jstack output. The output says no deadlock detected. I will try that site for analyzing the jstack.
Even a normal running Jenkins has many BLOCKED threads. If that is normal I don't know. We have a test Jenkins instance running on Java 11. That one does not have any BLOCKED threads. Our production Jenkins is running Java 8u181. torsdag 18. juli 2019 11.04.16 UTC+2 skrev Ivan Fernandez Calvo følgende: > > In that dump I can not see which thread is blocking the others, the jstack > output has a reference on each thread that said what thread is the blocker > on each thread (- locked <0x00000000> a java.lang.Object), you can try to > analyze those thread dump with https://fastthread.io/index.jsp or other > online tools to see if you see something relevant, it looks like there is a > deadlock. > > https://dzone.com/articles/how-to-read-a-thread-dump > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d1a855fe-34fb-4e88-973f-8c2b8fa0ab22%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
