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

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBDS-4085 at 10/6/16 1:54 PM:
-----------------------------------------------------------

Picked a random error...

{code}org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jsf [985]
{code}

...and tried to install a bunch of the m2e, wtp, and jsf-related things from Red Hat Central. Successfully installed... but that was over 20 mins ago and I'm still waiting for Eclipse to restart after the install. Something is seriously wrong here. [~rgrunber] can you suggest how best to see what's happening on startup? 

Tried {code}./eclipse -debug -consolelog -console{code} but not getting very helpful output: [^restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt]


was (Author: nickboldt):
Picked a random error...

{code}org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jsf [985]
{code}

...and tried to install a bunch of the m2e, wtp, and jsf-related things from Red Hat Central. Successfully installed... but that was over 20 mins ago and I'm still waiting for Eclipse to restart after the install. Something is seriously wrong here. [~rgrunber] can you suggest how best to see what's happening on startup? 

Tried {code}./eclipse -debug -consolelog -console{code} but not getting very helpful output. 

> 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, 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)