That looks to be a message from an attempt to dynamic import * from the tomcat bundle. That slowdown may be occuring from large numbers of class loads that result in dynamic package resolution.
Tom
----- Original message -----
From: Chamila Adhikarinayake via osgi-dev <osgi-dev@mail.osgi.org>
Sent by: osgi-dev-boun...@mail.osgi.org
To: osgi-dev@mail.osgi.org
Cc:
Subject: [osgi-dev] Startup delay due to osgi resolving
Date: Thu, Feb 7, 2019 5:56 AM
Hi All,I'm currently trying to migrate our product to work on jdk 11 and as a part of this effort upgraded the osgi framework (upgrading from equinox osgi version 3.9.1.v20130814-1242). We managed to upgrade the components and start the pack but currently we see high startup time (startup freezes in the middle for some additional time). we suspect it is due to bundle wiring.I checked the bundle status using ss command and all the bundles were in Active state.Then I enabled osgi debug logs for wiring (org.eclipse.osgi/resolver/wiring) and notice one component trying to wire to same component repeatedlyFollowing is a part of the log. similar repeated logs for different components can be seen during this startup freeze time . (I attached the full log)RESOLVER: Wirings for resolved bundles:Resourceosgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"Wiring[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]RESOLVER: Wirings for resolved bundles:Resourceosgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"Wiring[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]RESOLVER: Wirings for resolved bundles:Resourceosgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"Wiring[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]RESOLVER: Wirings for resolved bundles:Resourceosgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"Wiring[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]RESOLVER: Wirings for resolved bundles:Resourceosgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"Wiring[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]Can anyone please help me in identifying the problem and why it tries to wire to same package (any additional methods to narrowdown the issue). Same tomcat version was used in the old OSGI version but didn't see this kind of freezing in the middle.Thanks a lot_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev