[jbosstools-issues] [JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up

Nick Boldt (JIRA) issues at jboss.org
Thu Oct 6 17:14:00 EDT 2016 

    [ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13303727#comment-13303727 ] 

Nick Boldt commented on JBDS-4085:
----------------------------------

For example:

{code}
!ENTRY org.eclipse.linuxtools.docker.core 4 0 2016-10-06 14:13:15.493
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.linuxtools.docker.core [343]
  Unresolved requirement: Require-Bundle: com.google.guava; bundle-version="15.0.0"
    -> Bundle-SymbolicName: com.google.guava; bundle-version="15.0.0.v201403281430"
       com.google.guava [1242]
         Unresolved requirement: Import-Package: sun.misc; resolution:="optional"
  Bundle was not resolved because of a uses contraint violation.
  org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.linuxtools.docker.core [osgi.identity; type="osgi.bundle"; version:Version="2.1.0.201609081448"; osgi.identity="org.eclipse.linuxtools.docker.core"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources org.eclipse.osgi [osgi.identity; type="osgi.bundle"; version:Version="3.11.1.v20160920-1429"; osgi.identity="org.eclipse.osgi"; singleton:="true"] and jaxb-api [osgi.identity; type="osgi.bundle"; version:Version="2.2.12.b141001_1542"; osgi.identity="jaxb-api"] via two dependency chains.

Chain 1:
  org.eclipse.linuxtools.docker.core [osgi.identity; type="osgi.bundle"; version:Version="2.1.0.201609081448"; osgi.identity="org.eclipse.linuxtools.docker.core"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.eclipse.core.runtime)(bundle-version>=3.12.0))
     |
    provide: osgi.wiring.bundle: org.eclipse.core.runtime
  org.eclipse.osgi [osgi.identity; type="osgi.bundle"; version:Version="3.11.1.v20160920-1429"; osgi.identity="org.eclipse.osgi"; singleton:="true"]

Chain 2:
  org.eclipse.linuxtools.docker.core [osgi.identity; type="osgi.bundle"; version:Version="2.1.0.201609081448"; osgi.identity="org.eclipse.linuxtools.docker.core"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.glassfish.jersey.media.jersey-media-json-jackson)(bundle-version>=2.14.0))
     |
    provide: osgi.wiring.bundle; bundle-version:Version="2.22.2"; osgi.wiring.bundle="org.glassfish.jersey.media.jersey-media-json-jackson"
  org.glassfish.jersey.media.jersey-media-json-jackson [osgi.identity; type="osgi.bundle"; version:Version="2.22.2"; osgi.identity="org.glassfish.jersey.media.jersey-media-json-jackson"]
    import: (&(osgi.wiring.package=org.glassfish.jersey.message.filtering.spi)(&(version>=2.22.0)(!(version>=3.0.0))))
     |
    export: osgi.wiring.package=org.glassfish.jersey.message.filtering.spi; uses:=javax.xml.bind
  org.glassfish.jersey.ext.jersey-entity-filtering [osgi.identity; type="osgi.bundle"; version:Version="2.22.2"; osgi.identity="org.glassfish.jersey.ext.jersey-entity-filtering"]
    import: (osgi.wiring.package=javax.xml.bind)
     |
    export: osgi.wiring.package: javax.xml.bind
  jaxb-api [osgi.identity; type="osgi.bundle"; version:Version="2.2.12.b141001_1542"; osgi.identity="jaxb-api"]
	at org.eclipse.osgi.container.Module.start(Module.java:444)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
{code}
... is caused by these two plugins being co-installed:
* /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/plugins/org.eclipse.osgi_3.11.1.v20160920-1429.jar and 
* /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.glassfish.jersey.media.jersey-media-json-jackson_2.22.2.jar



> unresolved bundles, slow initial start up
> -----------------------------------------
>
>                 Key: JBDS-4085
>                 URL: https://issues.jboss.org/browse/JBDS-4085
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: rpm
>            Reporter: Václav Kadlčík
>         Attachments: restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, unresolved-max.out, unresolved-mid.out, unresolved-min.out, workspace-max.log, workspace-mid.log, workspace-min.log
>
>
> Tested:
>  * rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm
>  * rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-1.0/compose/Server/x86_64/os/)
> rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken).
> I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios:
>  * "min" in the name means minimal install rh-eclipse46-devstudio
>  * "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio"
>  * "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio
> As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example:
> initial start of rh-eclipse46: 40s
> same as above with rh-eclipse46-devstudio: 120s
> initial start of rh-eclipse46* except devstudio: 50s
> same as above with rh-eclipse46-devstudio: 140s
> Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway...



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

More information about the jbosstools-issues mailing list