Reference to ConfigurationAdmin not satisfied

[Roza Ghamari]

Hi 

I just made a bundle of my plugin and all the MongoEMF dependencies and successfully installed it on our custom RCP application. Previously, I tested my application running with pde product file on the same RCP application and it was working fine, other than the problem that i had to start mongoemf.query.mongodb plugin manually to have all the components enabled. 

However, now after I installed my plugin with mongoemf on our rcp application, I cannot start my services. Debugging the bundles and components I see that my ConfigurationAdmin service is unsatisfied. Here is the status:

osgi> comp 64
 Component[
 name = MyDefaultMongoDBConfigurator
 activate = activate
 deactivate = deactivate
 modified =
 configuration-policy = optional
 factory = null
 autoenable = true
 immediate = true
 implementation = MyDefaultConfigurator
 state = Unsatisfied
 properties =
 serviceFactory = false
 serviceInterface = null
 references = {
 Reference[name = ConfigurationAdmin, interface = org.osgi.service.cm.ConfigurationAdmin, policy = static, cardinality = 1..1, target = null, bind = bindConfigurationAdmin, unbind = null]
 }
 located in bundle = my.mongodb_0.0.1.201412040210 [368]
]
Dynamic information :
  *The component is NOT satisfied
  The following references are not satisfied:
    Reference[name = ConfigurationAdmin, interface = org.osgi.service.cm.ConfigurationAdmin, policy = static, cardinality = 1..1, target = null, bind = bindConfigurationAdmin, unbind = null]
  Component configurations :
    Configuration properties:
      component.name = MyDefaultMongoDBConfigurator
      component.id = 56
    Instances:

This causes the client and database providers to be unsatisfied as well as far as I understood. Could you please help me find out why ConfigurationAdmin reference is unsatisfied?

Thanks,

Roza

[Bryan Hunt]

What do you get when you issue an “ss” on the command line for configuration admin?

Bryan

--
You received this message because you are subscribed to the Google Groups "MongoEMF" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongoemf+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Roza Ghamari]

ss on the bundle I defined the configuration is Active and ss on  org.eclipse.osgi.services_3.3.100.v20130513-1956 is active too.

Should I look into any other bundles?

This is the ss on all Mongo bundles

osgi> ss eclipselabs

"Framework is launched."

id State       Bundle

345 ACTIVE      org.eclipselabs.emodeling.api_1.0.0.201307280847

346 ACTIVE      org.eclipselabs.emodeling.components_1.0.0.201307280847

347 RESOLVED    org.eclipselabs.emodeling.junit.util_1.0.0.201307280847

348 STARTING    org.eclipselabs.emodeling.log.core_1.0.0.201307280847

349 RESOLVED    org.eclipselabs.emodeling.query.simple_1.0.0.201307280847

350 ACTIVE      org.eclipselabs.emongo.api_1.0.0.201311181957

351 ACTIVE      org.eclipselabs.emongo.components_1.0.1.201311181957

           Fragments=352

352 RESOLVED    org.eclipselabs.emongo.configurator_1.0.0.201311181957

           Master=351

353 STARTING    org.eclipselabs.emongo.junit.config_1.0.0.201311181957

354 RESOLVED    org.eclipselabs.emongo.junit.util_1.0.0.201311181957

355 ACTIVE      org.eclipselabs.emongo.log_1.0.0.201311181957

356 STARTING    org.eclipselabs.eunit.junit.utils_1.0.0.201308191944

357 ACTIVE      org.eclipselabs.mongoemf.api_0.8.0.201403232117

358 ACTIVE      org.eclipselabs.mongoemf.builders_0.8.0.201403232117

359 ACTIVE      org.eclipselabs.mongoemf.converter_0.8.0.201403232117

360 ACTIVE      org.eclipselabs.mongoemf.handlers_0.8.0.201403232117

361 RESOLVED    org.eclipselabs.mongoemf.log_0.8.0.201403232117

362 ACTIVE      org.eclipselabs.mongoemf.query.mongodb_1.0.0.201403232117

363 ACTIVE      org.eclipselabs.mongoemf.query.simple_0.8.0.201403232117

364 ACTIVE      org.eclipselabs.mongoemf.streams_0.8.0.201403232117

And this is the ls on the relevant serices

45 Active org.eclipse.update.configurator.bundlegroup org.eclipse.update.configurator(bid=288)

46 Active org.eclipselabs.emodeling.factory org.eclipselabs.emodeling.components(bid=346)

47 Active org.eclipselabs.emodeling.uriHandlerConfigurator org.eclipselabs.emodeling.components(bid=346)

48 Unsatisfied org.eclipselabs.emodeling.components.uriMapping org.eclipselabs.emodeling.components(bid=346)

49 Unsatisfied org.eclipselabs.emongo.clientProvider org.eclipselabs.emongo.components(bid=351)

50 Unsatisfied org.eclipselabs.emongo.databaseProvider org.eclipselabs.emongo.components(bid=351)

51 Unsatisfied org.eclipselabs.emongo.idFactory org.eclipselabs.emongo.components(bid=351)

52 Active org.eclipselabs.emongo.components.client.metatype org.eclipselabs.emongo.components(bid=351)

53 Active org.eclipselabs.emongo.components.database.metatype org.eclipselabs.emongo.components(bid=351)

54 Active org.eclipselabs.emongo.components.id.metatype org.eclipselabs.emongo.components(bid=351)

55 Unsatisfied org.eclipselabs.emongo.junit.config org.eclipselabs.emongo.junit.config(bid=353)

56 Unsatisfied org.eclipselabs.emongo.log org.eclipselabs.emongo.log(bid=355)

57 Active org.eclipselabs.emongo.log.metatype org.eclipselabs.emongo.log(bid=355)

58 Active org.eclipselabs.mongoemf.builders.factory org.eclipselabs.mongoemf.builders(bid=358)

59 Active org.eclipselabs.mongoemf.converter org.eclipselabs.mongoemf.converter(bid=359)

60 Unsatisfied org.eclipselabs.mongoemf.handlers.mongoURIHandlerProvider org.eclipselabs.mongoemf.handlers(bid=360)

61 Active org.eclipselabs.mongoemf.query.mongodb org.eclipselabs.mongoemf.query.mongodb(bid=362)

62 Active org.eclipselabs.mongoemf.query.simple org.eclipselabs.mongoemf.query.simple(bid=363)

63 Active org.eclipselabs.mongoemf.streams.factory org.eclipselabs.mongoemf.streams(bid=364)

64 Unsatisfied MyDefaultMongoDBConfigurator my.mongodb(bid=368)

65 Unsatisfied my.Activator my.Activator(bid=368)

--
You received this message because you are subscribed to a topic in the Google Groups "MongoEMF" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mongoemf/wPq22UWvqV4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mongoemf+u...@googlegroups.com.

[Bryan Hunt]

I need to see the output of ss on the configuration admin (cm) bundle.

Bryan

 Reference[name = ConfigurationAdmin, interface =org.osgi.service.cm.ConfigurationAdmin, policy = static, cardinality = 1..1, target =null, bind = bindConfigurationAdmin, unbind = null]


 }
 located in bundle = my.mongodb_0.0.1.201412040210 [368]
]
Dynamic information :
  *The component is NOT satisfied
  The following references are not satisfied:


    Reference[name = ConfigurationAdmin, interface =org.osgi.service.cm.ConfigurationAdmin, policy = static, cardinality = 1..1, target =null, bind = bindConfigurationAdmin, unbind = null]


  Component configurations :
    Configuration properties:
      component.name = MyDefaultMongoDBConfigurator
      component.id = 56
    Instances:



This causes the client and database providers to be unsatisfied as well as far as I understood. Could you please help me find out why ConfigurationAdmin reference is unsatisfied?

Thanks,

Roza

-- 

You received this message because you are subscribed to the Google Groups "MongoEMF" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongoemf+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to a topic in the Google Groups "MongoEMF" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mongoemf/wPq22UWvqV4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mongoemf+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.