Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Why doesn't ConfigAdmin start?
Why doesn't ConfigAdmin start? [message #1757979] Wed, 22 March 2017 14:00
Thomas Quarendon is currently offline Thomas QuarendonFriend
Messages: 4
Registered: January 2017
Junior Member
We've got a problem that we're trying to understand.
We split our eclipse bundles between front end ones that are "eclipse aware" and backend ones that are plain OSGi bundles.
In order to get configuration information to the "backend" we use ConfigAdmin.

The difficulty that we have is that the org.eclipse.equinox.cm bundle never actually gets activated, it remains in "Resolved", so our backend services don't get configured, or in some cases even started (if they have the "REQUIRED" configuration policy).

We fail to understand what's going on. I *thought* I understood quite a lot about OSGi, but so far we've failed to truly understand this.

From the osgi console:
lb org.eclipse.equinox.cm
758|Resolved | 4|Configuration Admin (1.1.200.v20160324-1850)

So I have an implementation of config admin, it's just not started.
Manually starting it from the console makes things spring into life.

The only solution we know about is that we edit the "product" file to set a start level of 3 for the org.eclipse.equinox.cm, which appears to have the effect of ensuring that it is started.
However, we don't really want to do this. What we have is an "add-on", it isn't a "product", so what we're doing is editing the "product" file of something we don't control, just to see if it works. What we are writing is intended to be installed from the marketplace, or using "Install new software" etc.

We include "org.eclipse.equinox.cm" in our feature file, but there doesn't seem to be any way to make it auto start, which seems odd.

All of our bundles get activated fine. Maybe they are activated because they have the "Activate this plug-in when one of its classes is loaded" tick box ("Bundle-ActivationPolicy: lazy" in the MANIFEST). That's not relevant for the config admin bundle though, even if we could change it. Other OSGi services such as SCR get started fine (all our OSGi service declaration and consumption is done using declarative services).

What are we missing?
Is there a way to do this? To ensure that there is a running ConfigAdmin service, or force org.eclipse.equinox.cm to start?

Thanks.
Previous Topic:Supply Subject to login modules using LoginContextFactory
Next Topic:p2 - can't resolve org.eclipse.equinox.internal.provisional.configurator
Goto Forum:
  


Current Time: Mon Nov 12 18:40:56 GMT 2018

Powered by FUDForum. Page generated in 0.02255 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top