It’s not the mqtt binding, it’s the embedded broker. Moquette is very verbose when it comes to client connections with an already known client id but an invalid session.
I got in contact with the author and this is already changed, but not yet available for OH. You might just reduce the log level for that bundle (forum Search).
I’m on day 2 of my OH 2.4 experiments and getting 5 of these messages alongside every MQTT message - and I’ve only got openhab and nodered connected on a single pi. I hate to imagine what it looks like once I’ve got all 20 or so of my mqtt devices connected!
Will this be “going away” anytime?
David - it seems (from other threads) that you recommend using mosquitto over the embedded broker - this seems like one more reason to shy away from the built in one?
Looks like this problem still exists. Any news on this topic? My dirty workaround for this topic is, that I’m removing the /var/lib/openhab2/mqttembedded.bin file. It’s fine for me, because I don’t store data in MQTT… but that’s really dirty.
Funnily this is a new issue. Because the original one (wrong logging class) was fixed by me on the moquette broker, the hackish log hide-away we did on OH is not working anymore with the new version.