Yes, in openhabian.conf
Update: I haven’t seen this issue for some days, but moments ago it reappeared while I was stress testing the Hue binding.
openhab> threads | grep upnp-main-queue "upnp-main-queue" Id=371383 in RUNNABLE "pipe-grep upnp-main-queue" Id=374317 in RUNNABLE openhab> threads 371383 Thread 371383 upnp-main-queue RUNNABLE Stacktrace: java.util.concurrent.LinkedTransferQueue.awaitMatch line: 652 java.util.concurrent.LinkedTransferQueue.xfer line: 616 java.util.concurrent.LinkedTransferQueue.poll line: 1294 org.jupnp.QueueingThreadPoolExecutor$1.run line: 194 java.lang.Thread.run line: 833
So after reading:
I’m now suspecting this is also caused by:
This would mean it’s a bug in openjdk 17, not in openHAB, and there’s nothing we can easily do about it.
You gotta be kidding me, now:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 11216 openhab 20 0 1318172 472096 4528 S 256.2 47.4 4740:45 java
top -H -p 11216:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 25409 openhab 20 0 1318172 471856 4528 R 99.7 47.4 93:36.83 upnp-main-queue 30546 openhab 20 0 1318172 471856 4528 R 99.7 47.4 15:19.09 safeCall-queue
Hit by both cases.
3 posts were split to a new topic: JS issues after OH4 upgrade
Dear community members, please respect forum policy / posting rules.
Stay on topic and stay tight. The topic is FAQ here.
For anything not strictly related and of relevance to the FAQ, open your own threads.
Same if you want to discuss any of the FA questions in more detail.
When you do in wide-ranged or overview-like threads like this one, it’s quickly becoming an unreadable mess.
You might also want to add to the FAQ that old and incompatible OH 3.x .jar/.kar files in the
/addons dir (or installed via the Marketplace) should be removed/updated. They can cause a lot of issues as observed in: Endless loop during start of OH4.0.2 service after upgrade from OH4.0.1
I wonder if this should be done by the upgrade processes in the various installation methods. They can move them to a different folder perhaps (they should not delete them). And of course they should log out that it’s moved them.
Because it causes such a significant problem, and the end user is going to have to do something to manually download and install the newer version anyway, I don’t see that much of a down side. Shall I open an issue or is there something obvious here I’m not seeing that makes it a bad idea?
Yes I agree that this should be handled better so I welcome the issue.
2 posts were split to a new topic: Upgrade questions