Circular reference compability layer & zwave

Dear All,

Since last week I’m not able to start openhab2 anymore (online dist). I get many errors stating:

2016-08-29 14:56:10.724 [ERROR] [org.openhab.core.compat1x ] - [org.openhab.core.compat1x.eventbridge(8)] Circular reference detected, getService returning null 2016-08-29 14:56:10.762 [WARN ] [org.openhab.core.compat1x ] - FrameworkEvent WARNING - org.openhab.core.compat1x org.osgi.framework.ServiceException: org.apache.felix.scr.impl.manager.SingleComponentManager.getService() returned a null service object

Nest, weather, astro2, mqtt and http work everytime after reboot. But zwave and systeminfo do nothing. PaperUI works and removing and adding zwave only tells me the following line:
2016-08-29 14:56:27.880 [INFO ] [core.karaf.internal.FeatureInstaller] - Installed 'openhab-binding-zwave’
Nothing more.

Sometimes it just starts without error, but with the same behavior, no zwave or systeminfo.
Sometimes it gives xml database read errors on zwave:
2016-08-29 15:07:18.212 [WARN ] [ig.xml.osgi.XmlDocumentBundleTracker] - The XML document '/ESH-INF/thing/philio_pst02b_0_0.xml' in module 'org.openhab.binding.zwave' could not be parsed: : Exception in opening zip file: /opt/openHAB/userdata/cache/org.eclipse.osgi/166/1/bundleFile com.thoughtworks.xstream.io.StreamException: : Exception in opening zip file: /opt/openHAB/userdata/cache/org.eclipse.osgi/166/1/bundleFile
But also on many other files in openhab, not only zwave.

This is a manual install from snapshots. Anyone have a pointer what I can do? I have no Idea what I can check next, don’t want to do a clean install because many item definitions are made in PaperUI and not in item files.

Thanks,
Wouter

Thinking about it, the ones that work are using .item files. Systeminfo and zwave are configured using paperui or habmin in the openhab internal database. Could there be something wrong in there? Is there a way to check it?

FYI A few days ago I opened an issue on the circular reference problem.

Please see here - I hope that the issue is solved. If not, please report!