Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (athena.apache.org: domain of pierre.derop@gmail.com
 designates 72.14.220.156 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=m/AFr1sI38c6b0eaNTu2szHcrEnOyKiqFn70l2y9Mv3wp7CwdJ5LK4h0MaNWlJp5Jk
         /3odyjbKGwzg/i/mjme3rBnjDQnszCaMkslFudEujl37cM2EgbAt+lcXxapAqIO5IFLU
         jN1rf8A7TzOqlO439hqMa51Xx/Y+qCXQLaxME=
MIME-Version: 1.0
In-Reply-To: <v2g8203224e1004240249i480559e8p6465a435465ffb04@mail.gmail.com>
References: <v2g8203224e1004240249i480559e8p6465a435465ffb04@mail.gmail.com>
Date: Sat, 24 Apr 2010 12:09:22 +0200
Message-ID: <k2w8203224e1004240309z9942709ewd0cc6567b1a96cd3@mail.gmail.com>
Subject: Re: Issue with ConfigAdmin 1.2.4 ?
From: Pierre De Rop <pierre.derop@gmail.com>
To: dev@felix.apache.org
Content-Type: multipart/alternative; boundary=00221597529ae7efe90484f8bcb3

--00221597529ae7efe90484f8bcb3
Content-Type: text/plain; charset=ISO-8859-1

just to tell that I also tested with the latest ConfigAdmin from trunk, and
it also seems that an update is missed:

[LogService/4] Scheduling task Update:
pid=MyFactoryPid.1512b9c3-12f9-4671-8346-eec609d579f8
[LogService/4]
UpdateConfiguration(MyFactoryPid.1512b9c3-12f9-4671-8346-eec609d579f8)
scheduled
[LogService/4] Updated configuration
MyFactoryPid.1512b9c3-12f9-4671-8346-eec609d579f8 to update #3
[LogService/4] Running task Update:
pid=MyFactoryPid.1512b9c3-12f9-4671-8346-eec609d579f8
[LogService/4] Configuration
MyFactoryPid.1512b9c3-12f9-4671-8346-eec609d579f8 at modification #3 has
already been updated to update #3, nothing to be done anymore.
[LogService/4] Scheduling task Fire ConfigurationEvent:
pid=MyFactoryPid.1512b9c3-12f9-4671-8346-eec609d579f8
[LogService/4] Running task Fire ConfigurationEvent:
pid=MyFactoryPid.1512b9c3-12f9-4671-8346-eec609d579f8

/pierre


On Sat, Apr 24, 2010 at 11:49 AM, Pierre De Rop <pierre.derop@gmail.com>wrote:

> Hello everyone, and Felix;
>
> I am using ConfigAdmin 1.2.4, and I have written a test case which is using
> a ManagedServiceFactory, and consists in updating a Factory Configuration
> object.
> Something like:
>
> Configuration cf = configAdmin.createFactoryConfiguration(m_factoryPid,
> null);
> cf.update(new Properties() {{ put("foo", "bar"); }});
>
> And then, a little bit later, I update again the cf object, like this:
>
> cf.update(new Properties() {{ put("foo", "bar2"); }});
>
> So, most of the time, this test works fine. However, some times, the last
> update seems to be missed, and I see the following CM logs:
>
> [LogService/4] Scheduling task Update:
> pid=MyFactoryPid.c57f6e36-6e1a-4904-912f-26b021913087
> [LogService/4] Running task Update:
> pid=MyFactoryPid.c57f6e36-6e1a-4904-912f-26b021913087
> [LogService/4] Configuration
> MyFactoryPid.c57f6e36-6e1a-4904-912f-26b021913087 has already been updated,
> nothing to be done anymore.
> [LogService/4] Scheduling task Fire ConfigurationEvent:
> pid=MyFactoryPid.c57f6e36-6e1a-4904-912f-26b021913087
> [LogService/4] Running task Fire ConfigurationEvent:
> pid=MyFactoryPid.c57f6e36-6e1a-4904-912f-26b021913087
>
> So, I have checked if some pending issues were addressing this eventual
> problem, and I came across the issue FELIX-1545.
> So, my question is the following:
>
> is my problem related to the FELIX-1545 issue ? if not, then should I open
> a Jira issue ?
>
> thanks;
> /pierre
>

--00221597529ae7efe90484f8bcb3--