Hi James, thank you for your answer. No, the configuration is only used for one service. We debugged a little bit further and saw a strange behavior. The breakpoint was in the ConfigurationSupport.configurationEvent(event) method (see line 278 in http://grepcode.com/file/repo1.maven.org/maven2/org.apache.felix/org.apache.felix.scr/1.8.2/org/apache/felix/scr/impl/config/ConfigurationSupport.java#ConfigurationSupport ) .... The target and oldTargetPID looked like this:
successful case: targetPID: org.test.my.component.myComponent oldTargetPID: org.test.my.component.myComponent unsuccessful case: targetPid: org.test.my.component.myComponent oldTargetPID: org.test.my.component.myComponent.1f309340-04f9-4be6-b354-be67081a9232 For some reason, sometimes the pid is the factory pid and sometimes the normal pid. Any ideas? Best regards, Thomas 2015-05-12 13:56 GMT+02:00 James Carman <ja...@carmanconsulting.com>: > You aren't sharing one configuration file for multiple services are you? > On Tue, May 12, 2015 at 3:11 AM Thomas <johnnyenglish...@gmail.com> wrote: > >> Hey again, >> >> we investigate a little bit, but couldn't find the final solution. But we >> could extract some logs that might be helpful for someone with deeper >> knowledge of karaf/felix here? As I mentioned before, the problem appears >> only from time to time. We compared the logs from a successful and a failed >> update: >> >> successful update: http://pastebin.com/EPVzenPL >> failed update: http://pastebin.com/MYWi1TAc >> >> The problem seems to be the configadmin. In both cases, after updating >> the configuration there are 5 update events (CM_UPDATED). Every time (and >> we tested that a couple of times) the last event is for the SCR bundle, the >> update is successful. In every other case, the config update wasn't >> successful. Is it possible that there is some kind of race condition, maybe >> with the artifact installer? >> >> Thanks in advance and best regards, >> Thomas >> >> 2015-05-08 14:04 GMT+02:00 Thomas <johnnyenglish...@gmail.com>: >> >>> Hi, >>> >>> we recently updated the Karaf version from 2.3.5 to 2.4.2 in our >>> application. Since this change, the configuration update mechanism isn't >>> working properly anymore for us. I tried to update one property through >>> archaius and through the ssh interface (config:edit ...). I can see the >>> changed value in the configuration overview (Status -> Configuration) if I >>> open the webconsole, but the service itself has still the old value (OSGI >>> -> Services). It seems like the modify method isn't called. >>> >>> The strange thing is, from time to time it works. We have some >>> integration tests and some tests (which modifies the config) are green. The >>> same code worked fine with the old karaf version. Does anybody have an idea >>> if there is an issue with the config admin? >>> >>> Our Service looks like this: http://pastebin.com/5SWvTDQy ... We use >>> this as a ServiceFactory. Does anybody has an idea why the modify method >>> isn't called (every time)? >>> >>> Best regards, >>> Thomas >>> >> >>
