May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24414) Have JolokiaMBeanServerConnection support single response for setAttribute

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24414?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24414: -------------------------------- Fix Version/s: 4.5.0.AM1 > Have JolokiaMBeanServerConnection support single response for setAttribute > -------------------------------------------------------------------------- > > Key: JBIDE-24414 > URL: https://issues.jboss.org/browse/JBIDE-24414 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Fix For: 4.5.0.AM1 > > > Currently it is expecting a List of response always but it can also be a single response. -- 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 Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23869: ------------------------------------- Sorry I didn't see this earlier. I don't think there's anything we can do here. The best we can ask for is that the exception include the entire json response... but I'm not sure you'll think that is a big improvement. And also I think we're out of time. > 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-24301) Error while building jbosstools-openshift-4.4.3

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24301 at 5/11/17 2:27 PM: ------------------------------------------------------------------- [~jyoti-jboss] did you follow my steps to the letter? I have no other explanation than that you didnt, can't explain how you could end up having a directory {code} jbosstools-build-jbosstools-4.4.3.x {code} Please do exactly as told above, nothing else. You should end up having a directory {code} jbosstools-build {code} and within that directory, a git repository that's checked out in the master branch, no 4.4.3.x branch, no jbosstools-build-jbosstools-4.4.3.x directory (that you even have 2 within each other). was (Author: adietish): [~jyoti-jboss] did you follow my steps to the letter? I have no other explanation than that you didnt, can't explain how you could end up having a directory {code} jbosstools-build-jbosstools-4.4.3.x {code} Please do exactly as told above, nothing else. You should end up have a directory {code} jbosstools-build {code} and within that directory, a git repository that's checked out in the master branch, no 4.4.3.x branch, no jbosstools-build-jbosstools-4.4.3.x directory (that you even have 2 within each other). > Error while building jbosstools-openshift-4.4.3 > ----------------------------------------------- > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > Attachments: Error.PNG, issues.PNG, issues.txt, jbosstools-build.png, org.jboss.ide.eclipse.as.management.as7.png, target-platform.png > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24413) No space left on device for some rhel7-devstudio-releng slaves

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24413?page=com.atlassian.jira.plugi... ] Josef Kopriva edited comment on JBIDE-24413 at 5/11/17 2:14 PM: ---------------------------------------------------------------- Hi [~nickboldt], I was looking at that slave and it was running for one day and hudson workspace has 51GB, attaching screenshots with disk usage in workspace. !DiskUsageOnSlave.png|thumbnail! We should start cleaning after jobs, if it is possible, otherwise it would be just a matter of time, until we ran in the same issue with bigger drive. was (Author: jkopriva): Hi [~nickboldt], I was looking at that slave and it was running for one day and hudson workspace has 51GB, attaching screenshots with disk usage in workspace. !DiskUsageOnSlave.png|thumbnail! > No space left on device for some rhel7-devstudio-releng slaves > -------------------------------------------------------------- > > Key: JBIDE-24413 > URL: https://issues.jboss.org/browse/JBIDE-24413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.Final > Reporter: Nick Boldt > Assignee: Josef Kopriva > Fix For: 4.5.0.AM1 > > Attachments: DiskUsageOnSlave.png > > > JIRA to track infrequent failures due to slaves getting their disks full. > Will collect data over time in this spreadsheet: > https://docs.google.com/spreadsheets/d/1YGptkrWlUR3W03J-Mj-_xxzgsMrPwmbMl... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24413) No space left on device for some rhel7-devstudio-releng slaves

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24413?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24413: ---------------------------------- Attachment: DiskUsageOnSlave.png > No space left on device for some rhel7-devstudio-releng slaves > -------------------------------------------------------------- > > Key: JBIDE-24413 > URL: https://issues.jboss.org/browse/JBIDE-24413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.Final > Reporter: Nick Boldt > Assignee: Josef Kopriva > Fix For: 4.5.0.AM1 > > Attachments: DiskUsageOnSlave.png > > > JIRA to track infrequent failures due to slaves getting their disks full. > Will collect data over time in this spreadsheet: > https://docs.google.com/spreadsheets/d/1YGptkrWlUR3W03J-Mj-_xxzgsMrPwmbMl... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24413) No space left on device for some rhel7-devstudio-releng slaves

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24413?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-24413: --------------------------------------- Hi [~nickboldt], I was looking at that slave and it was running for one day and hudson workspace has 51GB, attaching screenshots with disk usage in workspace. !DiskUsageOnSlave.png|thumbnail! > No space left on device for some rhel7-devstudio-releng slaves > -------------------------------------------------------------- > > Key: JBIDE-24413 > URL: https://issues.jboss.org/browse/JBIDE-24413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.Final > Reporter: Nick Boldt > Assignee: Josef Kopriva > Fix For: 4.5.0.AM1 > > Attachments: DiskUsageOnSlave.png > > > JIRA to track infrequent failures due to slaves getting their disks full. > Will collect data over time in this spreadsheet: > https://docs.google.com/spreadsheets/d/1YGptkrWlUR3W03J-Mj-_xxzgsMrPwmbMl... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24413) No space left on device for some rhel7-devstudio-releng slaves

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24413?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24413: ------------------------------------ New failure due to no space on device: May 11, 2017 12:37:34 PM https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/computer/rhe... No space left on device 13:33:56 (about an hour after the build started) https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > No space left on device for some rhel7-devstudio-releng slaves > -------------------------------------------------------------- > > Key: JBIDE-24413 > URL: https://issues.jboss.org/browse/JBIDE-24413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.Final > Reporter: Nick Boldt > Assignee: Josef Kopriva > Fix For: 4.5.0.AM1 > > > JIRA to track infrequent failures due to slaves getting their disks full. > Will collect data over time in this spreadsheet: > https://docs.google.com/spreadsheets/d/1YGptkrWlUR3W03J-Mj-_xxzgsMrPwmbMl... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24439) Block PRs for merge untill the Jenkins build is successful

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24439: ---------------------------------- Summary: Block PRs for merge untill the Jenkins build is successful Key: JBIDE-24439 URL: https://issues.jboss.org/browse/JBIDE-24439 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.5.0.AM1 Reporter: Nick Boldt Assignee: Jeff MAURY Fix For: 4.5.0.AM1 As discussed in this thread [1], we'd like to implement *Protected Branches* and *Required Status Checks* [2] for some jbosstools-* projects. [1] http://lists.jboss.org/pipermail/jbosstools-dev/2017-May/011948.html [2] https://help.github.com/articles/defining-the-mergeability-of-pull-requests/ We will therefore need to document some requirements in jbosstools-devdoc about how to properly submit PRs when version-bumping is required: {quote}Make sure if your PR requires a version bump that the PR includes TWO commits. One for the change, and one for the version bump. That way the pair of commits can be built in the PR build and verify it works, AND when cherry picking the commit across branches, you can pick only the change and not the version-bump commit too. {quote} And we need to decide if we want to do what Fuse Tools does and require that PRs be reviewed before they can be merged, if we're ready to have that additional overhead on every PR. [~jeffmaury] as project lead can you state which project(s) you'd like to see changed in github, and which ones should be changed as such: * jbosstools-_____ ** Protected Branch = master ** Required Status Check(s) = ....? (which checks do we want) ** PR reviews required = [true/false] >From that list of projects / requirements, we can then create subtask JIRAs to track the workj & the changes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24348) Docker New and Noteworthy for 4.4.4.Final

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24348?page=com.atlassian.jira.plugi... ] Jeff Johnston commented on JBIDE-24348: --------------------------------------- Create N&N for Docker 4.4.4.Final > Docker New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24348 > URL: https://issues.jboss.org/browse/JBIDE-24348 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Priority: Critical > Fix For: 4.4.4.Final > > > Jeff Johnston, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker 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 Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker 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 Docker 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 Docker 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 Docker, 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-24348) Docker New and Noteworthy for 4.4.4.Final

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24348?page=com.atlassian.jira.plugi... ] Jeff Johnston closed JBIDE-24348. --------------------------------- Resolution: Done > Docker New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24348 > URL: https://issues.jboss.org/browse/JBIDE-24348 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Priority: Critical > Fix For: 4.4.4.Final > > > Jeff Johnston, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker 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 Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker 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 Docker 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 Docker 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 Docker, 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