Did a clean checkout of the official OpenEMS today. I started a clean Edge (without configuration) and I got the following error for several times:
2021-11-19 10:03:53,765 [artLevel] INFO [org.apache.felix.http.jetty ] Started Jetty 9.4.43.v20210629 at port(s) HTTP:18080 on context path / [minThreads=8,maxThreads=200,acceptors=1,selectors=4]
2021-11-19 10:03:55,248 [artLevel] WARN [ntmanager.ComponentManagerImpl] bundle io.openems.edge.core:1.0.0.202111190849 (75)[io.openems.edge.core.componentmanager.ComponentManagerImpl(1)] : Could not get service from ref [io.openems.edge.common.component.ComponentManager, io.openems.edge.common.component.OpenemsComponent, io.openems.edge.common.jsonapi.JsonApi, org.osgi.service.cm.ConfigurationListener]
2021-11-19 10:03:55,249 [artLevel] ERROR [ROOT ] bundle org.apache.felix.scr:2.1.30 (163) Circular reference detected trying to get service [io.openems.edge.predictor.api.manager.PredictorManager, io.openems.edge.common.component.OpenemsComponent, io.openems.edge.common.jsonapi.JsonApi]
stack of references: ServiceReference: [io.openems.edge.predictor.api.manager.PredictorManager, io.openems.edge.common.component.OpenemsComponent, io.openems.edge.common.jsonapi.JsonApi]
ServiceReference: [io.openems.edge.common.component.ComponentManager, io.openems.edge.common.component.OpenemsComponent, io.openems.edge.common.jsonapi.JsonApi, org.osgi.service.cm.ConfigurationListener]
It looks like OSGI has detected a circular depedancy. On the second start I did not get anymore errors and the edge comes up fine. Having a look at the felix console → OSGI → Components I see that the default bundles are active and that all references have been satisfied. It seems that OSGI has solved the circular dependency at some point in time. So I thought I found a hint within the configuration. But I can’t find any references within the configuration.
Just for interest, is there any easy and short explanation what has happend here?
Thanks, Chris