Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3F292200D37 for ; Thu, 9 Nov 2017 18:33:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3D9EE160BEF; Thu, 9 Nov 2017 17:33:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 835CA1609C8 for ; Thu, 9 Nov 2017 18:33:04 +0100 (CET) Received: (qmail 86968 invoked by uid 500); 9 Nov 2017 17:33:03 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 86957 invoked by uid 99); 9 Nov 2017 17:33:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Nov 2017 17:33:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B448BD525B for ; Thu, 9 Nov 2017 17:33:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ocnJsRZkguNe for ; Thu, 9 Nov 2017 17:33:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id B0C305FE2F for ; Thu, 9 Nov 2017 17:33:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 9D515E0D50 for ; Thu, 9 Nov 2017 17:33:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 18527240D6 for ; Thu, 9 Nov 2017 17:33:00 +0000 (UTC) Date: Thu, 9 Nov 2017 17:33:00 +0000 (UTC) From: "Tim Moloney (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KARAF-5474) features being configured twice MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 09 Nov 2017 17:33:05 -0000 [ https://issues.apache.org/jira/browse/KARAF-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246115#comment-16246115 ] Tim Moloney commented on KARAF-5474: ------------------------------------ I think that I figured it out. I think that it is a configuration issue in the stock configuration of Karaf Container (apache-karaf-4.0.10.tar.gz). etc/org.apache.karaf.features.cfg contains: #configCfgStore=true which I think means that the default setting is for the features service to write feature configurations to the configuration directory, etc. etc/config.properties contains: felix.fileinstall.dir = ${karaf.etc} which means that the fileinstall service will monitor the etc directory for changes. I believe that the combination of these two settings causes the following: the features service sends the configuration to configuration admin (first config) the features service writes the configuration to etc the fileinstall service sees the new file in etc the file install service write the configuration to configuration admin (second config) Setting configCfgStore=false fixes everything. So in the end, the two issues I asked about in my original email were related. The second issue was causing the first. > features being configured twice > ------------------------------- > > Key: KARAF-5474 > URL: https://issues.apache.org/jira/browse/KARAF-5474 > Project: Karaf > Issue Type: Bug > Components: karaf-feature > Affects Versions: 4.0.10 > Reporter: Tim Moloney > > Feature configurations are being sent twice to the service factories with two different service pids. > Example: > If a feature has the following config element: > {{}} > then {{FooServiceFactory.update(String pid, Dictionary properties)}} will be called twice. Each call with have the same {{properties}}, but different {{pid}} s. > See the [thread|http://mail-archives.apache.org/mod_mbox/karaf-user/201711.mbox/%3C76720540-cf2a-1a0b-196b-9448396aeced%40nanthrax.net%3E] in the mailing list. -- This message was sent by Atlassian JIRA (v6.4.14#64029)