[SOLVED] MQTT Broker Moquette offline after upgrade to 2.5M3

[Andrew_Rowe]

Restarting OpenHAB has caused the embedded mqtt server to go offline again. This time I do not see the same error message about a file lock causing the problem
unstalling the broker caused this

9:15:40.238 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mqtt:systemBroker:embedded-mqtt-broker' changed from OFFLINE (CONFIGURATION_ERROR): The system connection with the name embedded-mqtt-broker doesnt exist anymore. to REMOVING
19:15:40.239 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mqtt:systemBroker:embedded-mqtt-broker' changed from REMOVING to REMOVED
19:15:40.243 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mqtt:topic:a2b851fe' changed from OFFLINE (BRIDGE_OFFLINE) to UNINITIALIZED
19:15:40.252 [ERROR] [rnal.common.AbstractInvocationHandler] - An error occurred while calling method 'Runnable.run()' on 'org.eclipse.smarthome.core.thing.internal.ThingManagerImpl$$Lambda$822/2099136298@16b8d157': org.openhab.binding.mqtt.generic.internal.handler.GenericMQTTThingHandler cannot be cast to org.openhab.binding.mqtt.handler.AbstractBrokerHandler
java.lang.ClassCastException: org.openhab.binding.mqtt.generic.internal.handler.GenericMQTTThingHandler cannot be cast to org.openhab.binding.mqtt.handler.AbstractBrokerHandler
	at org.openhab.binding.mqtt.internal.MqttBrokerHandlerFactory.lambda$0(MqttBrokerHandlerFactory.java:83) ~[?:?]
	at java.util.WeakHashMap.forEach(WeakHashMap.java:1025) ~[?:?]
	at java.util.Collections$SynchronizedMap.forEach(Collections.java:2647) ~[?:?]
	at org.openhab.binding.mqtt.internal.MqttBrokerHandlerFactory.removeHandler(MqttBrokerHandlerFactory.java:83) ~[?:?]
	at org.eclipse.smarthome.core.thing.binding.BaseThingHandlerFactory.unregisterHandler(BaseThingHandlerFactory.java:258) ~[?:?]
	at org.eclipse.smarthome.core.thing.internal.ThingManagerImpl.lambda$5(ThingManagerImpl.java:811) ~[?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
	at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:152) [133:org.openhab.core:2.5.0.M3]
	at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [133:org.openhab.core:2.5.0.M3]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
19:15:40.258 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mqtt:topic:3d1078c8' changed from OFFLINE (BRIDGE_OFFLINE) to UNINITIALIZED
19:15:40.260 [ERROR] [rnal.common.AbstractInvocationHandler] - An error occurred while calling method 'Runnable.run()' on 'org.eclipse.smarthome.core.thing.internal.ThingManagerImpl$$Lambda$822/2099136298@584ba5a8': org.openhab.binding.mqtt.generic.internal.handler.GenericMQTTThingHandler cannot be cast to org.openhab.binding.mqtt.handler.AbstractBrokerHandler
java.lang.ClassCastException: org.openhab.binding.mqtt.generic.internal.handler.GenericMQTTThingHandler cannot be cast to org.openhab.binding.mqtt.handler.AbstractBrokerHandler
	at org.openhab.binding.mqtt.internal.MqttBrokerHandlerFactory.lambda$0(MqttBrokerHandlerFactory.java:83) ~[?:?]
	at java.util.WeakHashMap.forEach(WeakHashMap.java:1025) ~[?:?]
	at java.util.Collections$SynchronizedMap.forEach(Collections.java:2647) ~[?:?]
	at org.openhab.binding.mqtt.internal.MqttBrokerHandlerFactory.removeHandler(MqttBrokerHandlerFactory.java:83) ~[?:?]
	at org.eclipse.smarthome.core.thing.binding.BaseThingHandlerFactory.unregisterHandler(BaseThingHandlerFactory.java:258) ~[?:?]
	at org.eclipse.smarthome.core.thing.internal.ThingManagerImpl.lambda$5(ThingManagerImpl.java:811) ~[?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
	at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:152) [133:org.openhab.core:2.5.0.M3]
	at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [133:org.openhab.core:2.5.0.M3]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
19:15:40.263 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mqtt:systemBroker:embedded-mqtt-broker' changed from REMOVED to UNINITIALIZED
19:15:40.265 [WARN ] [ng.mqtt.handler.AbstractBrokerHandler] - Trying to dispose handler mqtt:systemBroker:embedded-mqtt-broker but connection is already null. Most likely this is a bug.
19:15:40.278 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mqtt:systemBroker:embedded-mqtt-broker' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)

check out WARN at 19:15:40:265

Most likely this is a bug

So anyhow… even though this time I did not see a error about the file being locked, (I might have missed it) stopping openhab, deleting the bin file, clearing the cache and restarting OpenHAB found my old mqtt broker in the inbox
Like the warning message above says… most likely this is a bug
my issue on git doesn’t seem to be drawing much attention

Also, I have another user having a similar problem but his started on an older version and he has since upgraded to 2.5M3 in an attempt to fix it
details here

[SOLVED] MQTT Embedded Crashed Will Not Restart

I haven’t cleared the cache yet; I end up with issues to fix every time I do. But I can ignore a few things for the time being. Once I get tired of looking at them I’ll get brave and try removing them.

anyhow… checked out code owners file and who is the developer for the embedded mqtt broker… none other then David Graeff
that is not sounding hopeful for getting this fixed as it seems David has lost interest in OpenHAB
see here

Next generation design: A Paper UI replacement proposal

Yannick is developing the unified UI for openHAB. My proposal here is a lot more sophisticated. I have identified problems in the backend http interface, proposed new API endpoints, modernized and simplified OH core code. But OH core development is slow as hell. (The core maintainers are busy fighting Java. I can understand that. They do not have time to develop new features or replace grandpa-aged subsystems.) I’m no longer participating in core development and I’m developing my own smarthome…