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 <[email protected]>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 >
