On the latest 5.0.2.-1, after a few days of running. I have sonos and wemo. Jvm itself over 4Gb after a few days…. I know about the upnp issues but was surprised to see all these logging threads.
It’s not default but nothing that I changed would have anything to do with the high thread count. There was no activity in the logs during the time when I took the histogram. I don’t do anything special for upnp.
I know about the upnp issues but was just surprised to see that log4j was somehow affected. 20 million is just huge. It was using over 4Gb on my system after forced GC. I’ve disabled all the upnp stuff for now and everything works fine, except for my sonos and wemo stuff.
I will try to check if I see something comparable on my side.
But since the last fixes, and the recent snapshot beginning early in November, I’ve don’t experience anymore issue with upnp. My openhab installation is stable for at least 7-10 days, memory not growing to much, and everything works ok : Sonos, etc.
I ask this because I was thinking that upnp regression was introduce after 5.0.2.
So this is perhaps another issue, but not the one fixes recently.
I see the M‑SEARCH changes I didn’t realize they were supposed to be in this version. I do also have a WiiM device which has always has issues with the binding. Fortunately WiiM has an http API that can be used instead.
I will re-enable it after a few more days I just want to see if everything is stable with it disabled. What I didn’t understand was why the 20million Slf4jLogger threads should be associated with the upnp issue.