[
https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832889#comment-15832889
]
Carsten Ziegeler commented on FELIX-5507:
-----------------------------------------
Afaik we're not doing any isolation at all and we're using non-Liberty
Websphere. But the framework is running within a webapp and should be
completely isolated from the container. So we have a single bundle space with a
single config admin service. As said in all other scenarios this is working
fine, just this single setup does not work.
And interestingly restarting the config admin bundle resolves the problem and
the service gets visible.
I'm not entirely sure whether this is really a DS problem and switching to the
system bundle as a workaround indicates to me that this has something to do
with service hooks, but so far I couldn't find any.
> 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)
