Andre Dietisheim created JBIDE-13763: ---------------------------------------- Summary: openshift-java-client: exception does not say to what server it was trying to connect Key: JBIDE-13763 URL: https://issues.jboss.org/browse/JBIDE-13763 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.0.Alpha2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.0.Alpha2 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: {code} 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 {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira