OsgiControllerImpl creates too many BundleStartTask
---------------------------------------------------

                 Key: SLING-1039
                 URL: https://issues.apache.org/jira/browse/SLING-1039
             Project: Sling
          Issue Type: Bug
    Affects Versions: JCR Install 2.0.4
            Reporter: Bertrand Delacretaz
            Priority: Minor


If a bundle cannot be started (for example because of missing dependencies), 
the OsgiControllerImpl keeps retrying to start it, every time its 
executeScheduledOperations() method is called.

This is ok (though we might want to lower the frequency of these calls when 
that happens), but on every cycle a BundleStartTask is created for each bundle, 
and it's not useful in this case.

This causes the INFO log to be filled with "Successfully executed 
BundleStartTask" messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to