[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Roland Grunberg updated JBDS-4085:
----------------------------------
Attachment: disable-uses-by-default.patch
> 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
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: disable-uses-by-default.patch, restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, rh-eclipse46-devstudio10.2.log.20161028-1611.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
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Roland Grunberg updated JBDS-4085:
----------------------------------
Attachment: (was: disable-uses-by-default.patch)
> 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
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: disable-uses-by-default.patch, restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, rh-eclipse46-devstudio10.2.log.20161028-1611.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
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Roland Grunberg updated JBDS-4085:
----------------------------------
Attachment: disable-uses-by-default.patch
> 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
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: disable-uses-by-default.patch, restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, rh-eclipse46-devstudio10.2.log.20161028-1611.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
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Roland Grunberg commented on JBDS-4085:
---------------------------------------
[^disable-uses-by-default.patch]
With this new patch, startup times went from around 3m50s to 18s. They also seemed to be sustained even after doing an installation of other content. The only change was that I needed to disable the older uses constraint checking from o.e.o.compatibility.state as well.
> 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
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: disable-uses-by-default.patch, restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, rh-eclipse46-devstudio10.2.log.20161028-1611.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
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Roland Grunberg updated JBDS-4085:
----------------------------------
Attachment: (was: disable-uses-by-default.patch)
> 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
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: disable-uses-by-default.patch, restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, rh-eclipse46-devstudio10.2.log.20161028-1611.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
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Roland Grunberg updated JBDS-4085:
----------------------------------
Attachment: disable-uses-by-default.patch
> 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
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: disable-uses-by-default.patch, disable-uses-by-default.patch, restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, rh-eclipse46-devstudio10.2.log.20161028-1611.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
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (JBIDE-22762) JMX remote call results (and others) cannot be copied using Cmd+C
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22762?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-22762.
---------------------------------
Resolution: Done
I've made a commit for this, which should work.
> JMX remote call results (and others) cannot be copied using Cmd+C
> ------------------------------------------------------------------
>
> Key: JBIDE-22762
> URL: https://issues.jboss.org/browse/JBIDE-22762
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
>
> I was verifying JBIDE-22549 which was supposed to add support for Ctrl+C in JMX remote call results. This doesn't work for me on Mac. Right-click -> Copy does work though.
> What I did was:
> 1. Start EAP 7
> 2. Connect in JMX Navigator
> 3. Go to MBeans -> jboss.as -> naming
> 4. Double click the mbean
> 5. Execute jndiView
> In the result window, I am not able to copy anything using Cmd+C, but I can copy using right-click -> Copy.
> I asked [~rhopp] to try this for me on Linux. But he got stuck on failed jmx connection of his local EAP 7 server (reported here: JBIDE-22761). And then I tried a similar thing in the Properties view and it turns out that I can't copy there either. Then I asked Radim to check that and he confirmed he cannot copy from Properties view using Ctrl+C on linux.
> Then I tried some more and noticed that in some occasions I can do that:
> For example if I select the active JMX connection in JMX Navigator, go to Properties view, expand Memory and select a row, I can copy with Cmd+C. But if I select an MBean and then click a row in the Properties view, I cannot copy with Cmd+C.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (JBIDE-22762) JMX remote call results (and others) cannot be copied using Cmd+C
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22762?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-22762:
--------------------------------
Fix Version/s: 4.4.2.AM3
> JMX remote call results (and others) cannot be copied using Cmd+C
> ------------------------------------------------------------------
>
> Key: JBIDE-22762
> URL: https://issues.jboss.org/browse/JBIDE-22762
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
>
> I was verifying JBIDE-22549 which was supposed to add support for Ctrl+C in JMX remote call results. This doesn't work for me on Mac. Right-click -> Copy does work though.
> What I did was:
> 1. Start EAP 7
> 2. Connect in JMX Navigator
> 3. Go to MBeans -> jboss.as -> naming
> 4. Double click the mbean
> 5. Execute jndiView
> In the result window, I am not able to copy anything using Cmd+C, but I can copy using right-click -> Copy.
> I asked [~rhopp] to try this for me on Linux. But he got stuck on failed jmx connection of his local EAP 7 server (reported here: JBIDE-22761). And then I tried a similar thing in the Properties view and it turns out that I can't copy there either. Then I asked Radim to check that and he confirmed he cannot copy from Properties view using Ctrl+C on linux.
> Then I tried some more and noticed that in some occasions I can do that:
> For example if I select the active JMX connection in JMX Navigator, go to Properties view, expand Memory and select a row, I can copy with Cmd+C. But if I select an MBean and then click a row in the Properties view, I cannot copy with Cmd+C.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (JBIDE-22762) JMX remote call results (and others) cannot be copied using Cmd+C
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22762?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-22762:
-----------------------------------
Assignee: Rob Stryker
> JMX remote call results (and others) cannot be copied using Cmd+C
> ------------------------------------------------------------------
>
> Key: JBIDE-22762
> URL: https://issues.jboss.org/browse/JBIDE-22762
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
>
> I was verifying JBIDE-22549 which was supposed to add support for Ctrl+C in JMX remote call results. This doesn't work for me on Mac. Right-click -> Copy does work though.
> What I did was:
> 1. Start EAP 7
> 2. Connect in JMX Navigator
> 3. Go to MBeans -> jboss.as -> naming
> 4. Double click the mbean
> 5. Execute jndiView
> In the result window, I am not able to copy anything using Cmd+C, but I can copy using right-click -> Copy.
> I asked [~rhopp] to try this for me on Linux. But he got stuck on failed jmx connection of his local EAP 7 server (reported here: JBIDE-22761). And then I tried a similar thing in the Properties view and it turns out that I can't copy there either. Then I asked Radim to check that and he confirmed he cannot copy from Properties view using Ctrl+C on linux.
> Then I tried some more and noticed that in some occasions I can do that:
> For example if I select the active JMX connection in JMX Navigator, go to Properties view, expand Memory and select a row, I can copy with Cmd+C. But if I select an MBean and then click a row in the Properties view, I cannot copy with Cmd+C.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months