Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-1039

OsgiControllerImpl creates too many BundleStartTask

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • JCR Installer 3.0.0
    • JCR Installer 3.0.0
    • None
    • None

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bdelacretaz Bertrand Delacretaz
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: