e: log4j bug causes deadlock?!? (was: which sort of application bugs
hang wotaskd?)
Hmmm, looks like we are not the only one who got bit by that thing in tender
parts: http://stackoverflow.com/a/7397857
On 25. 10. 2016, at 10:59 PM, OC <o...@ocs.cz<mailto:o...@ocs.cz>> wrote:
Chuck,
On
Hmmm, looks like we are not the only one who got bit by that thing in tender
parts: http://stackoverflow.com/a/7397857
> On 25. 10. 2016, at 10:59 PM, OC wrote:
>
> Chuck,
>
> On 24. 10. 2016, at 18:23, Chuck Hill wrote:
>
>> Running “sudo jstack –F ”
Chuck,
On 24. 10. 2016, at 18:23, Chuck Hill wrote:
> Running “sudo jstack –F ” should dump a trace of all threads.
> Should…
Luckily, it did; just it is sort of weird that it identifies threads by name in
the deadlock report, but by some unknown ID (perhaps hash of