[jbosstools-issues] [JBoss JIRA] (JBIDE-24306) Cannot connect to JMX through OpenShift Server adapter to a project without route specified
Rob Stryker (JIRA)
issues at jboss.org
Thu May 4 15:32:01 EDT 2017
[ https://issues.jboss.org/browse/JBIDE-24306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402224#comment-13402224 ]
Rob Stryker commented on JBIDE-24306:
-------------------------------------
I re-ran it a few times and now i get this non-error error...
{code}
[INFO]
[INFO] >>> fabric8-maven-plugin:3.1.80.redhat-000013:build (default) > initialize @ camel-ose-springboot-xml >>>
[INFO]
[INFO] <<< fabric8-maven-plugin:3.1.80.redhat-000013:build (default) < initialize @ camel-ose-springboot-xml <<<
[INFO]
[INFO] --- fabric8-maven-plugin:3.1.80.redhat-000013:build (default) @ camel-ose-springboot-xml ---
[INFO] F8: Using OpenShift build with strategy S2I
[INFO] F8: spring-boot: Using fat jar packaging as the spring boot plugin is using `repackage` goal execution
[INFO] F8: Running generator spring-boot
[INFO] F8: spring-boot: Using Docker image registry.access.redhat.com/jboss-fuse-6/fis-java-openshift:2.0-5 as base / builder
[INFO] Copying files to /home/rob/apps/eclipse/workspaces/fusejbidetest/Fused444/target/docker/camel-ose-springboot-xml/latest/build/maven
[INFO] Building tar: /home/rob/apps/eclipse/workspaces/fusejbidetest/Fused444/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
[INFO] F8: [camel-ose-springboot-xml:latest] "spring-boot": Created docker source tar /home/rob/apps/eclipse/workspaces/fusejbidetest/Fused444/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18.741 s
[INFO] Finished at: 2017-05-04T15:30:04-04:00
[INFO] Final Memory: 54M/709M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000013:build (default) on project camel-ose-springboot-xml: Execution default of goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000013:build failed: An error has occurred. connect timed out -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
{code}
> Cannot connect to JMX through OpenShift Server adapter to a project without route specified
> -------------------------------------------------------------------------------------------
>
> 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)
More information about the jbosstools-issues
mailing list