If your code sends its time in the resolver it generally means that the resolver has too much choice. This can happen that the same package is exported under different versions for example.
Certain configurations can turn pathological since the resolver is an NP
complete problem. In my experience taking a good look at the package
imports/exports and the service requirements tends to show that the resolver
has too many choices to make.
Kind regards,
Peter Kriens
> On 22 Oct 2018, at 19:43, Alain Picard via osgi-dev <osgi-dev@mail.osgi.org>
> wrote:
>
> We are experiencing some long startup time in our reafactored application
> that is now heavily using SCR.
>
> We have 125 projects with over 1200 Service Components and it takes about 2
> minutes to get any output in the console. Some quick analysis shows that its
> running the Felix ResolverImpl with something like 5-6 thread (that is with
> Equinox).
>
> I looked in that class but there doesn't seem to be any tracing code, only
> what appears to be some debugging code.
>
> Is this expected? If not what have others used to resolve this issue?
>
> Thanks
> Alain
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
