[jbosstools-issues] [JBoss JIRA] (JBIDE-24438) Server adapter: JMX connection is not working for OpenShift instance
Aurélien Pupier (JIRA)
issues at jboss.org
Mon Jun 12 05:45:00 EDT 2017
[ https://issues.jboss.org/browse/JBIDE-24438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419326#comment-13419326 ]
Aurélien Pupier commented on JBIDE-24438:
-----------------------------------------
it is working when using the CDK locally because the connection is providing a port.
it is not working when using open.paas.redhat.com as the connection does not provide any ports
> Server adapter: JMX connection is not working for OpenShift instance
> ---------------------------------------------------------------------
>
> Key: JBIDE-24438
> URL: https://issues.jboss.org/browse/JBIDE-24438
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Labels: jmx, jolokia, openshift_v3, server_adapter
> Fix For: 4.5.0.AM2
>
> Attachments: JMXForOpenSHiftWithoutPortNotWorking.mp4, ManualJMXConnectionWithoutPortWorking.mp4
>
>
> such as open.paas.redhat.com
> {noformat}
> java.io.IOException: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:camel-ose-springboot-xml-1-02ue1:8778/proxy/jolokia/: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> 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.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:camel-ose-springboot-xml-1-02ue1:8778/proxy/jolokia/: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:330)
> 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)
> ... 4 more
> Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:150)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> 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)
> ... 7 more
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
> at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 18 more
> {noformat}
> we can notice that the url used is https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:camel-ose-springboot-xml-1-02ue1:8778/proxy/jolokia/
> It should not contain the port 8443
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jbosstools-issues
mailing list