[ https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839729#comment-15839729 ]
Thomas Watson commented on FELIX-5507: -------------------------------------- I also agree with David and Felix. The system bundle context is only going to find all Config Admin services that are registered in the system. If you are running on a system that isolates applications, like I suspect is happening on WebSphere then that may get you a CA instance that does not apply to your application. > ConfigurationAdmin not visible to bundles > ----------------------------------------- > > Key: FELIX-5507 > URL: https://issues.apache.org/jira/browse/FELIX-5507 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) > Affects Versions: scr-2.0.8 > Reporter: Carsten Ziegeler > Fix For: scr-2.1.0 > > > We have one case where the extended bundles do not see the configuration > admin service. Interestingly the same application runs fine everywhere else, > but just on a special environment (windows, ibm java inside Websphere) we > have this problem reproducibly. > Using the system bundle context instead of the bundle context of the extended > bundle in ConfigAdminTracker solves the problem. > Interestingly only the bundles started last (2 out of probably 80) see the > configuration admin. > It could also be that a faulty service hook is involved, although I'm not yet > aware of such a hook -- This message was sent by Atlassian JIRA (v6.3.4#6332)