[jira] [Commented] (ARIES-1459) Installing subsystem with large number of constituents takes forever or gives out of memory

["John Ross (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARIES-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132643#comment-15132643 ] 

John Ross commented on ARIES-1459:
----------------------------------

Did upgrading to the latest version of the resolver help? If so, can I resolve this?

> Installing subsystem with large number of constituents takes forever or gives out of memory
> -------------------------------------------------------------------------------------------
>
>                 Key: ARIES-1459
>                 URL: https://issues.apache.org/jira/browse/ARIES-1459
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>    Affects Versions: subsystem-2.0.6
>            Reporter: David Bosschaert
>
> Installing a large subsystem that contains a lot of bundles can cause the resolution phase to run for hours and sometimes causes out of memory, even with a feature subsystem.
> I think this is caused by the fact that all the bundles inside the subsystem are attempted to be resolved in one shot. When you have 200+ bundles that gives an enormous resolution problem space.
> In a plain OSGi framework such a scenario can be helped by installing bundles in stages, making life easier for the resolver. 
> Maybe subsystems can support this too. We could use the 'start-order' directive on the Subsystem-Content header to guide resolution and only resolve bundles on the current start-order as we progress through those.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)