Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Fri, 17 Feb 2017 06:41:41 +0000 (UTC)
From: "Carsten Ziegeler (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <JIRA.13036564.1484919816000.106900.1487313701673@Atlassian.JIRA>
In-Reply-To: <JIRA.13036564.1484919816000@Atlassian.JIRA>
References: <JIRA.13036564.1484919816000@Atlassian.JIRA> <JIRA.13036564.1484919816583@jira-lw-us.apache.org>
Subject: [jira] [Commented] (FELIX-5507) ConfigurationAdmin might not be
 visible to SCR implementation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 17 Feb 2017 06:42:02 -0000


    [ https://issues.apache.org/jira/browse/FELIX-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871273#comment-15871273 ] 

Carsten Ziegeler commented on FELIX-5507:
-----------------------------------------

In rev 1783333 I've added a little bit of code to catch the situation and log an error. If we can agree at least on this change, I think we can close this issue

> ConfigurationAdmin might not be visible to SCR implementation
> -------------------------------------------------------------
>
>                 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
>            Assignee: 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
> Update: after some discussion, some issues in the framework have been identified, but also the SCR implementation is not 100% correct: as it is using the bundle context of the extended bundle, it might get a configuration admin which interface is not visible to SCR. Therefore it should revert to reflection to access the configuration admin.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)