I wonder if something is setting/changing/unsetting the bundle location on the configuration? Based on reports of other cycling behavior, I think this might happen if there’s a blueprint bundle also using the pid. If the bundle location is for instance set to another bundle and then unset repeatedly then DS will see the configuration as alternatingly visible/invisible to your DS component and activate/deactive it.
I’m not very familiar with karaf but I would try to turn up the config admin logging all the way and look for evidence about what is happening with the bundle location. hope this helps david jencks > On Sep 13, 2016, at 8:01 AM, Marc Durand <marc.dur...@gmail.com> wrote: > > I've been having a problem that I can't seem to resolve even after days of > troubleshooting. When Karaf starts up, some of my components are activated > (methods annotated with @Activate are called), then de-activated (methods > annotated with @Deactivate are called) and activated again - sometimes > multiple times. I see this in the log: > > 2016-09-13 10:46:07,624 INFO (CM Configuration Updater (ManagedService > Update: pid=[org.apache.aries.transaction]):::::::) > [DatabaseHelperFactoryImpl] activate: called > 2016-09-13 10:46:07,773 INFO (CM Configuration Updater (ManagedService > Update: pid=[org.apache.aries.transaction]):::::::) > [DatabaseHelperFactoryImpl] deactivate: called > 2016-09-13 10:46:07,783 INFO (CM Configuration Updater (ManagedService > Update: pid=[org.apache.aries.transaction]):::::::) > [DatabaseHelperFactoryImpl] activate: called > 2016-09-13 10:46:07,901 INFO (CM Configuration Updater (ManagedService > Update: pid=[org.apache.aries.transaction]):::::::) > [DatabaseHelperFactoryImpl] deactivate: called > 2016-09-13 10:46:07,911 INFO (CM Configuration Updater (ManagedService > Update: pid=[org.apache.aries.transaction]):::::::) > [DatabaseHelperFactoryImpl] activate: called > > Seeing "CM Configuration Updater (ManagedService Update: > pid=[org.apache.aries.transaction])" in the log makes me think that Aries > thinks its configuration has changed when in fact it has not. Is this a > bug? What can I do to troubleshoot/resolve this issue? > > Thanks in advance, > Marc > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Karaf-4-x-startup-Aries-causing-components-to-deactivate-and-re-activate-multiple-times-tp4047996.html > Sent from the Karaf - User mailing list archive at Nabble.com.
