-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
None
Most exceptions that occur while talking to OpenShift are not telling you to what server the client was talking to. They mostly simply repeat the path:
com.openshift.client.OpenShiftEndpointException: Could not request /api: java.net.ConnectException: Connection timed out at com.openshift.internal.client.RestService.request(RestService.java:103) at com.openshift.internal.client.RestService.request(RestService.java:91) at com.openshift.internal.client.RestService.request(RestService.java:72) at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34) at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:161) at com.openshift.client.utils.TestConnectionFactory.getConnection(TestConnectionFactory.java:31) at com.openshift.internal.client.ApplicationResourceIntegrationTest.setUp(ApplicationResourceIntegrationTest.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.junit.runners.model.FrameworkMethod$1.runReflectiv
- blocks
-
JBIDE-13819 include latest openshift-java-client in JBoss Tools
- Closed
- relates to
-
OSJC-39 openshift-java-client: cannot get json response from exception
- Closed