Hi,
We have a process in which our AEM 6.2 authoring server needs to perform a nightly backup. We notice that on the next day the 2 OSGI components that we need to publish content will have these states:
- ActivateListener (to decide what type of content to publish) - may be satisfied or active
- ConfigurationService - active
Is satisfied the same as "resolved" in an OSGI component life cycle? Is there a difference between satisfied and active - it seems that if things work correctly, the ActivateListener will proceed whether in a satisfied or active state.
What we have also noticed that in publishing a piece of content, the ActivateListener may before publishing be satisfied and then change to active upon publishing. Likewise, it can be active before publishing, then changes to satisfied.
Does it mean that the ActivateListener is not stable? Is there some other way beside looking at /system/console/components to determine if a component is truly in an "active" state? Should we expand each component and look at the "Activation" status?
We have relied on ConfigurationService to return a particular set property value and we have seen it as being only in active state, yet in our debug log, we have noticed that ConfigurationService may not be returning a value so the rest of the dependent logic is never processed.
How do we ensure that the states we see for components in /system/console/components are truly what they are?
Thank you.
