April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24306) Cannot connect to JMX through OpenShift Server adapter to a FIS project

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24306?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24306: ---------------------------------- Assignee: Rob Stryker > Cannot connect to JMX through OpenShift Server adapter to a FIS project > ----------------------------------------------------------------------- > > Key: JBIDE-24306 > URL: https://issues.jboss.org/browse/JBIDE-24306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.4.Final > > Attachments: image-2017-04-25-14-48-51-427.png, screenshot-1.png > > > !image-2017-04-25-14-48-51-427.png|thumbnail! > in log: > {noformat} > eclipse.buildId=10.4.0.AM3-v20170406-1058-B390 > java.version=1.8.0_112 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/C:/ws-devsuite-1.4.0-170425/ -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.jmx.core > Error > Tue Apr 25 14:47:14 CEST 2017 > An error occurred while opening the connection. > java.io.IOException: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324) > at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:80) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113) > 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) > Caused by: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage > at org.jolokia.client.J4pClient.mapException(J4pClient.java:333) > at org.jolokia.client.J4pClient.execute(J4pClient.java:198) > 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:311) > ... 5 more > Caused by: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage > at org.apache.http.impl.client.CloseableHttpClient.determineTarget(CloseableHttpClient.java:94) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55) > at org.jolokia.client.J4pClient.execute(J4pClient.java:190) > ... 8 more > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24306) Cannot connect to JMX through OpenShift Server adapter to a FIS project

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24306?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24306: ------------------------------- Fix Version/s: 4.4.4.Final > Cannot connect to JMX through OpenShift Server adapter to a FIS project > ----------------------------------------------------------------------- > > Key: JBIDE-24306 > URL: https://issues.jboss.org/browse/JBIDE-24306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Fix For: 4.4.4.Final > > Attachments: image-2017-04-25-14-48-51-427.png, screenshot-1.png > > > !image-2017-04-25-14-48-51-427.png|thumbnail! > in log: > {noformat} > eclipse.buildId=10.4.0.AM3-v20170406-1058-B390 > java.version=1.8.0_112 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/C:/ws-devsuite-1.4.0-170425/ -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.jmx.core > Error > Tue Apr 25 14:47:14 CEST 2017 > An error occurred while opening the connection. > java.io.IOException: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324) > at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:80) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113) > 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) > Caused by: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage > at org.jolokia.client.J4pClient.mapException(J4pClient.java:333) > at org.jolokia.client.J4pClient.execute(J4pClient.java:198) > 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:311) > ... 5 more > Caused by: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage > at org.apache.http.impl.client.CloseableHttpClient.determineTarget(CloseableHttpClient.java:94) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55) > at org.jolokia.client.J4pClient.execute(J4pClient.java:190) > ... 8 more > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24309) When editing a Json OpenShift instance config file, open it with Json Editor

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24309?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24309: ------------------------------------ It used to be that way before but it has proven to cause update issues as it is not easy to add listeners so that when the content is updated the corresponding resource is updated > When editing a Json OpenShift instance config file, open it with Json Editor > ---------------------------------------------------------------------------- > > Key: JBIDE-24309 > URL: https://issues.jboss.org/browse/JBIDE-24309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Fix For: 4.5.0.Final > > Attachments: image-2017-04-25-15-31-31-092.png > > > currently it is is opened with Text Editor > For instance when editing a Deployment config: > !image-2017-04-25-15-31-31-092.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24308) Disable "Import application" contextual menu on build config having no git url configured

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24308?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24308: ------------------------------- Fix Version/s: 4.5.0.AM1 > Disable "Import application" contextual menu on build config having no git url configured > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24308 > URL: https://issues.jboss.org/browse/JBIDE-24308 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Fix For: 4.5.0.AM1 > > Attachments: image-2017-04-25-15-25-07-634.png, image-2017-04-25-15-25-34-373.png > > > !image-2017-04-25-15-25-07-634.png|thumbnail! > it avoids to have an error dialog just after: > !image-2017-04-25-15-25-34-373.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24309) When editing a Json OpenShift instance config file, open it with Json Editor

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24309?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24309: ------------------------------- Fix Version/s: 4.5.0.Final > When editing a Json OpenShift instance config file, open it with Json Editor > ---------------------------------------------------------------------------- > > Key: JBIDE-24309 > URL: https://issues.jboss.org/browse/JBIDE-24309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Fix For: 4.5.0.Final > > Attachments: image-2017-04-25-15-31-31-092.png > > > currently it is is opened with Text Editor > For instance when editing a Deployment config: > !image-2017-04-25-15-31-31-092.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24217) Deployment config is not shown in OpenshiftExplorer, when service is deleted.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24217?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24217: ------------------------------- Story Points: 15 > Deployment config is not shown in OpenshiftExplorer, when service is deleted. > ----------------------------------------------------------------------------- > > Key: JBIDE-24217 > URL: https://issues.jboss.org/browse/JBIDE-24217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Radim Hopp > Assignee: Jeff MAURY > Fix For: 4.4.4.Final > > > When service is deleted (in Openshift Explorer), the whole tree node is removed (even though other resources still exist in openshift). > The Deployment config node is not even shown when "refresh" is used. Only thing that helps is removing whole Openshift connection and adding it back again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24217) Deployment config is not shown in OpenshiftExplorer, when service is deleted.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24217?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24217: ------------------------------- Sprint: devex #131 May 2017 > Deployment config is not shown in OpenshiftExplorer, when service is deleted. > ----------------------------------------------------------------------------- > > Key: JBIDE-24217 > URL: https://issues.jboss.org/browse/JBIDE-24217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Radim Hopp > Assignee: Jeff MAURY > Fix For: 4.4.4.Final > > > When service is deleted (in Openshift Explorer), the whole tree node is removed (even though other resources still exist in openshift). > The Deployment config node is not even shown when "refresh" is used. Only thing that helps is removing whole Openshift connection and adding it back again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24241) Server adapter not working when created from replication controller fallback

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24241?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24241: ------------------------------- Story Points: 10 > Server adapter not working when created from replication controller fallback > ---------------------------------------------------------------------------- > > Key: JBIDE-24241 > URL: https://issues.jboss.org/browse/JBIDE-24241 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Jan Richter > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.Final > > > When no service nor deployment config is available, it is possible to create a server adapter using replication controllers. A server adapter created this way errors on start with the following message: > {noformat} > An internal error occurred during: "Starting nodejs-1 (ReplicationController) at OpenShift 3 (192.168.42.24)". > deploymentconfigs "nodejs" not found deploymentconfigs "nodejs" not found > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24241) Server adapter not working when created from replication controller fallback

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24241?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24241: ------------------------------- Sprint: devex #131 May 2017 > Server adapter not working when created from replication controller fallback > ---------------------------------------------------------------------------- > > Key: JBIDE-24241 > URL: https://issues.jboss.org/browse/JBIDE-24241 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Jan Richter > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.Final > > > When no service nor deployment config is available, it is possible to create a server adapter using replication controllers. A server adapter created this way errors on start with the following message: > {noformat} > An internal error occurred during: "Starting nodejs-1 (ReplicationController) at OpenShift 3 (192.168.42.24)". > deploymentconfigs "nodejs" not found deploymentconfigs "nodejs" not found > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24298) Could not find "org.sonatype.tycho.m2e.feature.feature.group/0.9.0.201609061714" in the repositories of the current location

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24298?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-24298: ------------------------------------------- Now I see that the fuse tolling will require at least 0.8.1 https://github.com/jbosstools/jbosstools-fuse/pull/942 > Could not find "org.sonatype.tycho.m2e.feature.feature.group/0.9.0.201609061714" in the repositories of the current location > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24298 > URL: https://issues.jboss.org/browse/JBIDE-24298 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Reporter: Tomáš Sedmík > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.4.2.Final > > > Here http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho/ in _Composite*.xml_ files _0.9.0.201609061714_ version is not specified. > {code} > [INFO] Adding repository http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho > [INFO] Fetching compositeContent.xml from http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho/ (467B) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho... (5.89kB) > [ERROR] Failed to resolve target definition /home/fedora/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.4.2.Final/target-platform-4.4.2.Final-base.target: Could not find "org.sonatype.tycho.m2e.feature.feature.group/0.9.0.201609061714" in the repositories of the current location -> [Help 1] > {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 April 2017