8:30 a.m.
[
https://issues.jboss.org/browse/JBIDE-24438?page=com.atlassian.jira.plugi...
]
Aurélien Pupier commented on JBIDE-24438:
-----------------------------------------
{quote}I'm sorry, but I really don't understand the steps to replicate here.
{quote}
ok, steps were not very precised but I reported it quickly when I was in a conference. I
thought that there was enough information.
{quote}
What do you mean by "connect to open.paas.redhat.com with server adapters" ??
Do you mean create an openshift connection to open.paas.redhat.com and then create a
server adapter from one of the projects there?{quote}
Yes
{quote}Which project?{quote}
whatever projects providing a JMX connection. I know that the FIS ones are providing one.
{quote}
What is open.paas.redhat.com?{quote}
It is the internal Red Hat OpenShift server.
{quote}Is it the same as openshift.io?{quote}
no.
openshift.io was not released when i reported the issue and I still have no access to it
but I guess that it contains also on OpenSHift instance to which we can connect.
{quote}What credentials does this use?{quote}
everything is explained on the login page (that you can access when you are logged in to
the Red Hat vpn.
I provided an example with open.paas.redhat.com but I think that it applies to all
OpenShift instance that are not using a specific port number to connect to.
I cannot provide a screencast for now because it seems that FIS is broken of
open.paas.redhat.com and i don't have time to investigate which other kind of image I
can use.
{noformat}
Receiving source from STDIN as archive ...
==================================================================
Starting S2I Java Build .....
S2I source build with plain binaries detected
Copying binaries from /tmp/src to /deployments ...
cp: cannot stat '/tmp/src/*': No such file or directory
Aborting due to error code 1 for copying /tmp/src to /deployments
error: build error: non-zero (13) exit code from
registry.access.redhat.com/jboss-fuse-6/fis-java-openshift:2.0-5
{noformat}
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.AM1
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:c...:
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:c...:
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:c...
It should not contain the port 8443
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
3231
days inactive
3231
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Aurélien Pupier (JIRA)