[ https://issues.apache.org/jira/browse/SLING-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647342#action_12647342 ]
Bertrand Delacretaz commented on SLING-731: ------------------------------------------- Fixed in revision 713758, and the Exception that causes bundle.start to fail is now also logged. The drawback is that if a bundle is really missing a dependency, jcrinstall will try to restart it every second, until the dependency is available. We should probably use a retry count on the bundle restart, or slow down the queue processing when this happens - so leaving this issue open. > Active bundles queue must be reprocessed if bundle.start() fails > ---------------------------------------------------------------- > > Key: SLING-731 > URL: https://issues.apache.org/jira/browse/SLING-731 > Project: Sling > Issue Type: Bug > Components: JCR Install > Reporter: Bertrand Delacretaz > > In BundleResourceProcessor.startBundles, if Bundle.start() fails the bundle > is re-added to the activeBundles queue, but the needsRefresh flag is not set. > If several bundles which depend on each other fill this queue, it might > happen that the first one does not start because it needs another one that's > in the queue. > When that happens, the queue remains non-empty, but is never refresh if no > new bundles are detected. > The consequence is that some bundles might not be started until a new bundle > arrives which causes the needsRefresh flag to be set. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.