Uploaded image for project: 'OpenShift Java Client'
  1. OpenShift Java Client
  2. OSJC-44

openshift-java-client: exception does not say to what server it was trying to connect

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 2.1.0
    • 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
      

              adietish@redhat.com André Dietisheim
              adietish@redhat.com André Dietisheim
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: