May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1103) SAP tests are failing due to installation timeout

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1103: ---------------------------------------- Summary: SAP tests are failing due to installation timeout Key: JBTIS-1103 URL: https://issues.jboss.org/browse/JBTIS-1103 Project: JBoss Tools Integration Stack Issue Type: Bug Components: Fuse IDE, QE Affects Versions: 4.4.3.CR1 Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Fix For: 4.4.3.CR1 SAP tests are failing due to installation timeout. There is an issue with the new Eclipse where all installations take toooo long. See JBDS-4343 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4343) Installation hangs on 'Configuring toolingorg.eclipse.equinox.launcher.*'

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-4343?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-4343: ----------------------------------------- This is not only related to Devstudio installation. This affects all installations :( Is it already reported in Eclipse bugzilla? > Installation hangs on 'Configuring toolingorg.eclipse.equinox.launcher.*' > ------------------------------------------------------------------------- > > Key: JBDS-4343 > URL: https://issues.jboss.org/browse/JBDS-4343 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.4.0.AM2 > Environment: devstudio-10.4.0.AM2-v20170330-1543-B348-installer-standalone.jar > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.0.0.GA > > Attachments: install.png > > > The installer spends several minutes in this state: > !install.png|thumbnail! > Just for comparison > - AM1 installation takes total of about 2 minutes 15 seconds > - AM2 takes 5 minutes 40 seconds > There is no shortage of memory or disk I/O availability, the CPU is not topped off (even though AM2 eats up more CPU itself during this time). > DTRACE=true reveals nothing interesting really, this is what it says in the particular moment (notice how much time the operation takes): > {noformat} > Configuring toolingorg.eclipse.equinox.launcher.gtk.linux.x86_64 > Preparing to commit the provisioning operation. > Committing the provisioning operation. > Operation completed in 289855 ms. > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-23869: ----------------------------------------- {quote}Don't think we can do more as the request is rejected by OpenShift for authentication reason. You need to setup your OpenShift credentials on the JMX connection (HTTP header){quote} Do you mean that the OpenShift server is providing the "Invalid status type java.lang.String('Failure') recevived". I'm very sceptical on that. With this error the user has no idea that it is due to some authentication issue, so 2 possibilities: - OpenShift server is providing a bad response --> this need to be improved on OpenShift server side - the OpenShift server response is ate by Jolokia or JBoss Tools --> this need to be fixed in Jolokia or JBoss Tools > ClassCastException with Jolokia connection > ------------------------------------------ > > Key: JBIDE-23869 > URL: https://issues.jboss.org/browse/JBIDE-23869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: jmx, jolokia, openshift > Fix For: 4.4.4.Final > > Attachments: failure.png, image-2017-02-06-13-54-27-708.png > > > !image-2017-02-06-13-54-27-708.png|thumbnail! > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1102) Fuse: Fix/Adapt tests for Fuse Tooling 9.2.0

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-1102: ----------------------------------- Summary: Fuse: Fix/Adapt tests for Fuse Tooling 9.2.0 Key: JBTIS-1102 URL: https://issues.jboss.org/browse/JBTIS-1102 Project: JBoss Tools Integration Stack Issue Type: Bug Components: Fuse IDE, QE Affects Versions: 4.4.3.CR1 Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík Priority: Blocker Fix For: 4.4.3.Final There are some failures in automated tests - see https://docs.google.com/spreadsheets/d/1HQFxYixyfnuKAfRTAOklbGeCNAddp6Odr.... Fix them asap! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24369) LiveReload New and Noteworthy for 4.4.4.Final

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24369?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-24369. --------------------------------- Resolution: Rejected > LiveReload New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24369 > URL: https://issues.jboss.org/browse/JBIDE-24369 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Jeff MAURY > Assignee: Xavier Coulon > Priority: Critical > > Xavier Coulon, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed LiveReload JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for LiveReload, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for LiveReload by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24345 #comment Create N&N for LiveReload 4.4.4.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for LiveReload for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of LiveReload, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.4.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23869: ------------------------------------ Don't think we can do more as the request is rejected by OpenShift for authentication reason. You need to setup your OpenShift credentials on the JMX connection (HTTP header) > ClassCastException with Jolokia connection > ------------------------------------------ > > Key: JBIDE-23869 > URL: https://issues.jboss.org/browse/JBIDE-23869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: jmx, jolokia, openshift > Fix For: 4.4.4.Final > > Attachments: failure.png, image-2017-02-06-13-54-27-708.png > > > !image-2017-02-06-13-54-27-708.png|thumbnail! > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24360) Easymport New and Noteworthy for 4.4.4.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24360?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24360: ------------------------------- Fix Version/s: 4.4.4.Final > Easymport New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24360 > URL: https://issues.jboss.org/browse/JBIDE-24360 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: easymport > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.4.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Easymport JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Easymport, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Easymport by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24345 #comment Create N&N for Easymport 4.4.4.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Easymport for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of Easymport, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.4.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24317) Analyze capabilities replacement

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24317?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24317: ------------------------------- Fix Version/s: 4.5.0.AM1 > Analyze capabilities replacement > -------------------------------- > > Key: JBIDE-24317 > URL: https://issues.jboss.org/browse/JBIDE-24317 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.AM1 > > > Analyze how the capabilities features can be replaced when switching to the fabric8 client -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24359) Webservices / Rest New and Noteworthy for 4.4.4.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24359?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24359: ------------------------------- Fix Version/s: 4.4.4.Final > Webservices / Rest New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24359 > URL: https://issues.jboss.org/browse/JBIDE-24359 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.4.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Webservices / Rest JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Webservices / Rest, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Webservices / Rest by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24345 #comment Create N&N for Webservices / Rest 4.4.4.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Webservices / Rest for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of Webservices / Rest, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.4.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24349) Usage Analytics New and Noteworthy for 4.4.4.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24349?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24349: ------------------------------- Fix Version/s: 4.4.4.Final > Usage Analytics New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24349 > URL: https://issues.jboss.org/browse/JBIDE-24349 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: usage > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.4.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Usage Analytics JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Usage Analytics, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Usage Analytics by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24345 #comment Create N&N for Usage Analytics 4.4.4.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Usage Analytics for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of Usage Analytics, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.4.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2017