openHAB 5.1.0Mx: UPNP Issues

[Nadahar (Nadar)]

@reyhard

For me, it was also working for few days and yesterday it happened again. Here is dump from karaf 247.21 MB file on MEGA

I feared something like this - it doesn’t seem like dump-create includes monitors/locking information, which is essential to figure this out. I can’t find any arguments that you can use with dump-create to include it either. So, while this thread dump provides some insight, I can’t really figure out what’s blocking what.

Could you try the procedure I listed above instead?

@Nadahar

After some testing on my openHABian, I found this approach quite easy:

sudo ps -ax | grep bin/java

It will list a lot of stuff, what you’re interested in is the PID of the Java process running OH, which should be the very first thing it prints (in my case it was 726).

Then, once you have your PID, run (insert your PID number)

sudo jstack -l 726 > threaddump.txt

The thread dump is then in the file threaddump.txt in the folder you’re in when you run the

The -l parameter is what makes it include the information I need.

Edit: Your dump shows 18 threads that are considered blocked, but there are another 478 threads waiting for some lock to open. Not all over these are “wrong”, some mechanisms use waiting for a lock as a way to “pause” execution until a task is due, but without doubt, a portion of these should not be waiting, and are in effect stuck.