[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4085:
----------------------------------
After some time, the console finally completed and Eclipse failed to start: [^restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt]
Looks like most of the problem is 'could not resolve' and 'constraint violation' errors. Seems that by installing things via Central we end up with conflicting dependency chains between stuff in /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/ and stuff in ~/.eclipse/
> 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-...)
> 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)
9 years, 6 months
[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4085:
-----------------------------
Attachment: restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt
> 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-...)
> 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)
9 years, 6 months
[JBoss JIRA] (JBIDE-23150) Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23150?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23150 at 10/6/16 4:24 PM:
-------------------------------------------------------------------
[~bdshadow] good finding. Yes, I believe that you're right. This is not a bug but a conceptual "limitation" to what we would erroneously expect of it. Rejecting as *NOT_A_BUG*.
was (Author: adietish):
[~bdshadow] good finding. Yes, I believe that you're right. This is not a bug but a conceptual "limitation" to what we would expect of it. Rejecting as *NOT_A_BUG*.
> Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23150
> URL: https://issues.jboss.org/browse/JBIDE-23150
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: properties
> Fix For: 4.4.2.AM2
>
> Attachments: openshift-explorer-and-properties-both-stacked.png, properties-empty.png
>
>
> If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
> !openshift-explorer-and-properties-both-stacked.png!
> and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
> steps to reproduce:
> # ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
> # ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
> # EXEC: make Properties view visible
> # EXEC: make OpenShift explorer visible. Select an entry
> # EXEC: switch back to Properties view
> Result:
> Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
> !properties-empty.png!
> Only moving Properties view to a different (visual) container helps.
> the steps simply show a reliable way to reproduce it. I think there are more cases where this happens. Root cause could be in platform, not sure though.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23150) Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23150?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23150 at 10/6/16 4:23 PM:
-------------------------------------------------------------------
[~bdshadow] good finding. Yes, I believe that you're right. This is not a bug but a conceptual "limitation" to what we would expect of it. Rejecting as NOT_A_BUG.
was (Author: adietish):
[~bdshadow] good finding. Yes, I believe that you're right. This is not a bug but a conceptual "limitation" to what we would expect of it. Resolving as not-a-bug.
> Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23150
> URL: https://issues.jboss.org/browse/JBIDE-23150
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: properties
> Fix For: 4.4.2.AM2
>
> Attachments: openshift-explorer-and-properties-both-stacked.png, properties-empty.png
>
>
> If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
> !openshift-explorer-and-properties-both-stacked.png!
> and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
> steps to reproduce:
> # ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
> # ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
> # EXEC: make Properties view visible
> # EXEC: make OpenShift explorer visible. Select an entry
> # EXEC: switch back to Properties view
> Result:
> Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
> !properties-empty.png!
> Only moving Properties view to a different (visual) container helps.
> the steps simply show a reliable way to reproduce it. I think there are more cases where this happens. Root cause could be in platform, not sure though.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23150) Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23150?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23150 at 10/6/16 4:23 PM:
-------------------------------------------------------------------
[~bdshadow] good finding. Yes, I believe that you're right. This is not a bug but a conceptual "limitation" to what we would expect of it. Rejecting as *NOT_A_BUG*.
was (Author: adietish):
[~bdshadow] good finding. Yes, I believe that you're right. This is not a bug but a conceptual "limitation" to what we would expect of it. Rejecting as NOT_A_BUG.
> Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23150
> URL: https://issues.jboss.org/browse/JBIDE-23150
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: properties
> Fix For: 4.4.2.AM2
>
> Attachments: openshift-explorer-and-properties-both-stacked.png, properties-empty.png
>
>
> If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
> !openshift-explorer-and-properties-both-stacked.png!
> and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
> steps to reproduce:
> # ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
> # ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
> # EXEC: make Properties view visible
> # EXEC: make OpenShift explorer visible. Select an entry
> # EXEC: switch back to Properties view
> Result:
> Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
> !properties-empty.png!
> Only moving Properties view to a different (visual) container helps.
> the steps simply show a reliable way to reproduce it. I think there are more cases where this happens. Root cause could be in platform, not sure though.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23150) Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23150?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-23150.
--------------------------------------
Resolution: Rejected
Labels: properties (was: )
> Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23150
> URL: https://issues.jboss.org/browse/JBIDE-23150
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: properties
> Fix For: 4.4.2.AM2
>
> Attachments: openshift-explorer-and-properties-both-stacked.png, properties-empty.png
>
>
> If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
> !openshift-explorer-and-properties-both-stacked.png!
> and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
> steps to reproduce:
> # ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
> # ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
> # EXEC: make Properties view visible
> # EXEC: make OpenShift explorer visible. Select an entry
> # EXEC: switch back to Properties view
> Result:
> Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
> !properties-empty.png!
> Only moving Properties view to a different (visual) container helps.
> the steps simply show a reliable way to reproduce it. I think there are more cases where this happens. Root cause could be in platform, not sure though.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23150) Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23150?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23150:
------------------------------------------
[~bdshadow] good finding. Yes, I believe that you're right. This is not a bug but a conceptual "limitation" to what we would expect of it. Resolving as not-a-bug.
> Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23150
> URL: https://issues.jboss.org/browse/JBIDE-23150
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.2.AM2
>
> Attachments: openshift-explorer-and-properties-both-stacked.png, properties-empty.png
>
>
> If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
> !openshift-explorer-and-properties-both-stacked.png!
> and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
> steps to reproduce:
> # ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
> # ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
> # EXEC: make Properties view visible
> # EXEC: make OpenShift explorer visible. Select an entry
> # EXEC: switch back to Properties view
> Result:
> Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
> !properties-empty.png!
> Only moving Properties view to a different (visual) container helps.
> the steps simply show a reliable way to reproduce it. I think there are more cases where this happens. Root cause could be in platform, not sure though.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBTIS-873) Follow name convetions for archive files from devstudio
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-873?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-873.
------------------------------
Fix Version/s: 10.0.0.GA
(was: 10.0.0.Alpha1)
Resolution: Done
This is fixed in both 9.0.2.GA and the next Neon release (10.0.0.GA)
> Follow name convetions for archive files from devstudio
> -------------------------------------------------------
>
> Key: JBTIS-873
> URL: https://issues.jboss.org/browse/JBTIS-873
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 10.0.0.Alpha1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 10.0.0.GA, 9.0.2.GA
>
>
> Currently, the name is
> {code}
> devstudio-integration-stack-10.0.0.Alpha1-SNAPSHOT-earlyaccess.zip
> {code}
> I suggest to follow name conventions from devstudio, e.g.
> {code}
> devstudio-integration-stack-10.0.0.Alpha1-updatesite.zip
> devstudio-integration-stack-10.0.0.Alpha1-updatesite-earlyaccess.zip
> devstudio-integration-stack-10.0.0.Alpha1-standalone-installer.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months