Skip to content

Problem with Jama connection resulting in "Connection refused" #21

Description

@jmauersberger

Hi,

I have a problem in a specific environment connecting to the Jama cloud. I enabled HTTPClient logging and got something like this:

2018/07/09 09:49:07:334 EDT [DEBUG] RequestAddCookies - CookieSpec selected: default
2018/07/09 09:49:07:334 EDT [DEBUG] RequestAuthCache - Auth cache not set in the context
2018/07/09 09:49:07:334 EDT [DEBUG] PoolingHttpClientConnectionManager - Connection request: [route: {s}->https://XXXXX-sandbox.jamacloud.com:443][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 20]
2018/07/09 09:49:07:334 EDT [DEBUG] PoolingHttpClientConnectionManager - Connection leased: [id: 1][route: {s}->https://XXXXX-sandbox.jamacloud.com:443][total kept alive: 0; route allocated: 1 of 2; total allocated: 1 of 20]
2018/07/09 09:49:07:334 EDT [DEBUG] MainClientExec - Opening connection {s}->https://XXXXX-sandbox.jamacloud.com:443
2018/07/09 09:49:07:335 EDT [DEBUG] DefaultHttpClientConnectionOperator - Connecting to XXXXX-sandbox.jamacloud.com/52.40.8.52:443
2018/07/09 09:49:07:335 EDT [DEBUG] SSLConnectionSocketFactory - Connecting socket to XXXXX-sandbox.jamacloud.com/52.40.8.52:443 with timeout 0
2018/07/09 09:49:08:360 EDT [DEBUG] DefaultManagedHttpClientConnection - http-outgoing-1: Shutdown connection
2018/07/09 09:49:08:361 EDT [DEBUG] MainClientExec - Connection discarded
2018/07/09 09:49:08:361 EDT [DEBUG] PoolingHttpClientConnectionManager - Connection released: [id: 1][route: {s}->https://XXXXX-sandbox.jamacloud.com:443][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 20]
Jul 09, 2018 9:49:08 AM com.jamasoftware.services.restclient.httpconnection.ApacheHttpClient execute
SEVERE: Failed to execute with an exception org.apache.http.conn.HttpHostConnectException: Connect to XXXXX-sandbox.jamacloud.com:443 [XXXXX-sandbox.jamacloud.com/52.40.8.52] failed: Connection refused: connect
org.apache.http.conn.HttpHostConnectException: Connect to XXXXX-sandbox.jamacloud.com:443 [XXXXX-sandbox.jamacloud.com/52.40.8.52] failed: Connection refused: connect
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:158)
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 com.jamasoftware.services.restclient.httpconnection.ApacheHttpClient.execute(ApacheHttpClient.java:129)
at com.jamasoftware.services.restclient.httpconnection.ApacheHttpClient.get(ApacheHttpClient.java:153)
at com.jamasoftware.services.restclient.jamaclient.JamaClient.ping(JamaClient.java:78)

Any idea why that could be the case? Any experience?
Not that access via browser works fine.

Thanks Jan

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions