It seems that my problem was a bug of automatic bundles resolution in BndTools, Peter Kriens suggested to drop it and manage the bundles list by hand ( it was my first try with automatic resolution) and now ConfigAdmin works well and my first bricks are OK. Automatic resolution enabled 2 components in 2 versions: OSGi cmpn (4.2 & 4.3) and ConfigAdmin (1.4 & 1.6)
So by hand I kept the latest versions and now it seems OK , no more log entries and my tests are OK Kind regards and sorry for inconveniance Thanks Jerome J.MOLIERE - Mentor/J 2013/9/20 jerome moliere <[email protected]> > LogService bundle version is Apache Felix LogService 1.0.1 > > J.MOLIERE - Mentor/J > > > > 2013/9/20 Felix Meschberger <[email protected]> > >> Hi Jerome >> >> When using 1.6 you will get the exceptions logged unless (a) and/or (b) >> below apply. There is not setting for this in configuration admin. >> >> (a) would be a code bug and (b) is a feature of the log service used, >> which I cannot help with since I don't know which is used. >> >> Regards >> Felix >> >> Am 20.09.2013 um 08:36 schrieb jerome moliere: >> >> > Hi Felix, >> > thanks for your answer: >> > BndTools through automatic resolution deploys ConfigAdmin 1.4 & 1.6 , I >> > kill manually the 1.4 bundle. >> > I am using the WebConsole 3.1.8 (it's the one provided in the BndTools >> OBR >> > repositories) and I can't find any checkbox or anything for tuning the >> > level of exceptions.Is it a feature from the latest versions or is it a >> > property to pass to the JVM? >> > >> > Kind regards >> > Jerome >> > >> > >> > J.MOLIERE - Mentor/J >> > >> > >> > >> > 2013/9/20 Felix Meschberger <[email protected]> >> > >> >> Hi >> >> >> >> You don't tell us which version of the Felix Configuration Admin >> service >> >> bundle you are using, so I base my assumption on the latest release >> 1.6.0 >> >> >> >> Looking at the handleCallBackError and the ConfigurationManager.log >> method >> >> I would expect the exception (Throwable actually) to be passed to the >> >> LogService.log method. >> >> >> >> There may be two situations: >> >> >> >> (a) My assumption of passing the Throwable is wrong -- you might have >> to >> >> put a brak point in the handleCallBackError to validate this >> >> (b) Your LogService is not actually logging the throwable for some >> reason >> >> -- you might have to check your LogService to validate this >> >> >> >> Regards >> >> Felix >> >> >> >> Am 19.09.2013 um 18:29 schrieb jerome moliere: >> >> >> >>> Hi all felix gurus >> >>> I am using felix 4.2.1 and JDK 7 inside BndTools 2.1 running inside >> >> Eclipse >> >>> Juno SR2 on Linux x64 (ArchLinux 3.4 Kernel) >> >>> I am facing a strange error , ConfigAdmin raises exception during >> update >> >> of >> >>> my config >> >>> This message comes from the handleCallBackError() method. >> >>> The message is not very informative with : Unexpected problem updating >> >>> configuration" , it's logged inside the LoGService ... >> >>> I don't have more details about the problem. >> >>> Did someone encountered this problem ? >> >>> It may come from my code but the Web Console shows the config with the >> >>> right service.pid ,the ManagedService is succesfully registered . >> >>> I don't have any logs from my updated() method... >> >>> >> >>> Kind regards >> >>> Jerome >> >>> >> >>> >> >>> J.MOLIERE - Mentor/J >> >> >> >> >> >> >
