com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out

Atlassian JIRA | Lachlan Dally | 2 years ago
  1. 0

    *Stacktrace:* {code}2015-02-03 14:52:00,123 WARN [http-bio-8080-exec-2] [internal.integration.jira.DefaultJiraService] communicateWithJira Problem communicating with JIRA -- url: /confluence/rest/jira-integration/1.0/servers/c823ccbc-bcca-3d5d-9169-3f12fb15e747/projects | userName: admin | referer: http://localhost:8080/confluence/pages/createpage.action?spaceKey=ds&fromPageId=589832 com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:376) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:161) at com.atlassian.applinks.core.auth.ApplicationLinkRequestAdaptor.execute(ApplicationLinkRequestAdaptor.java:84) at com.atlassian.applinks.core.auth.oauth.ThreeLeggedOAuthRequest.execute(ThreeLeggedOAuthRequest.java:54) at com.atlassian.internal.integration.jira.DefaultJiraService$5.apply(DefaultJiraService.java:451) at com.atlassian.internal.integration.jira.DefaultJiraService$5.apply(DefaultJiraService.java:445) at com.atlassian.internal.integration.jira.DefaultJiraService.communicateWithJira(DefaultJiraService.java:702) at com.atlassian.internal.integration.jira.DefaultJiraService.getProjectsAsJson(DefaultJiraService.java:445) at com.atlassian.internal.integration.jira.rest.JiraServerResource.getProjectsMeta(JiraServerResource.java:43) 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:606) {code} *Steps to Reproduce:* # Start up JIRA from source in debug mode. # Start up Confluence, and create an application link between the two instances # Set the Socket Timeout in General Configuration to, for example, 20000 (20 seconds) # Create a project and issue in JIRA # Set a breakpoint in JIRA anywhere that's convenient and hit the breakpoint # Create a new page in Confluence and open up the network tab of your Browser # Create a JIRA Issues Macro in Confluence and search for the new project. Looking in the network tab of the browser's inspector, you'll see the following URL timing out after 10 seconds: {code}http://localhost:8090/jira/rest/api/2/issue/createmeta?projects.issuetypes{code} (Even after applying the workaround from https://jira.atlassian.com/browse/CONF-36316) If you apply the {{plugin.jira-integration.remote.timeout.socket}} system property, the timeout remains at 10 seconds, as the {{ConfluenceJiraSettings}} class doesn't provide a useful implementation of {{getProperty()}}

    Atlassian JIRA | 2 years ago | Lachlan Dally
    com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out
  2. 0

    *Stacktrace:* {code}2015-02-03 14:52:00,123 WARN [http-bio-8080-exec-2] [internal.integration.jira.DefaultJiraService] communicateWithJira Problem communicating with JIRA -- url: /confluence/rest/jira-integration/1.0/servers/c823ccbc-bcca-3d5d-9169-3f12fb15e747/projects | userName: admin | referer: http://localhost:8080/confluence/pages/createpage.action?spaceKey=ds&fromPageId=589832 com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:376) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:161) at com.atlassian.applinks.core.auth.ApplicationLinkRequestAdaptor.execute(ApplicationLinkRequestAdaptor.java:84) at com.atlassian.applinks.core.auth.oauth.ThreeLeggedOAuthRequest.execute(ThreeLeggedOAuthRequest.java:54) at com.atlassian.internal.integration.jira.DefaultJiraService$5.apply(DefaultJiraService.java:451) at com.atlassian.internal.integration.jira.DefaultJiraService$5.apply(DefaultJiraService.java:445) at com.atlassian.internal.integration.jira.DefaultJiraService.communicateWithJira(DefaultJiraService.java:702) at com.atlassian.internal.integration.jira.DefaultJiraService.getProjectsAsJson(DefaultJiraService.java:445) at com.atlassian.internal.integration.jira.rest.JiraServerResource.getProjectsMeta(JiraServerResource.java:43) 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:606) {code} *Steps to Reproduce:* # Start up JIRA from source in debug mode. # Start up Confluence, and create an application link between the two instances # Set the Socket Timeout in General Configuration to, for example, 20000 (20 seconds) # Create a project and issue in JIRA # Set a breakpoint in JIRA anywhere that's convenient and hit the breakpoint # Create a new page in Confluence and open up the network tab of your Browser # Create a JIRA Issues Macro in Confluence and search for the new project. Looking in the network tab of the browser's inspector, you'll see the following URL timing out after 10 seconds: {code}http://localhost:8090/jira/rest/api/2/issue/createmeta?projects.issuetypes{code} (Even after applying the workaround from https://jira.atlassian.com/browse/CONF-36316) If you apply the {{plugin.jira-integration.remote.timeout.socket}} system property, the timeout remains at 10 seconds, as the {{ConfluenceJiraSettings}} class doesn't provide a useful implementation of {{getProperty()}}

    Atlassian JIRA | 2 years ago | Lachlan Dally
    com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out
  3. 0

    h3. Step to reproduce: # Create a table with 30 row. # Fill all the table row with some word # Highlight one of the row and click the JIRA issue icon # Select the option {{Create X issues from this table}} # Then select create. +Expected result+ New JIRA issue will be created in JIRA project and the link will be added in the Confluence page. +Observed result+ New JIRA issues are created in JIRA project however no link are added in the Confleunce page. Sometimes the process will hang and you are force to refresh the page. An error is displayed: {quote}X issues have been created, but there are problems in adding them to the page. You can manually add them later using JIRA macro.{quote} The following will appear in the logs as well: {code} 2014-09-17 13:16:09,661 WARN [http-bio-8091-exec-1] [internal.integration.jira.DefaultJiraService] communicateWithJira Problem communicating with JIRA -- referer: http://new.com/display/WEB/test | url: /teamsite/rest/jira-integration/1.0/issues | userName: van.ly com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:376) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:161) {code} h3.Workaround The only available workaround is to manually add JIRA issue links to the page.

    Atlassian JIRA | 2 years ago | Jing Hwa [Atlassian]
    com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    h3. Step to reproduce: # Create a table with 30 row. # Fill all the table row with some word # Highlight one of the row and click the JIRA issue icon # Select the option {{Create X issues from this table}} # Then select create. +Expected result+ New JIRA issue will be created in JIRA project and the link will be added in the Confluence page. +Observed result+ New JIRA issues are created in JIRA project however no link are added in the Confleunce page. Sometimes the process will hang and you are force to refresh the page. An error is displayed: {quote}X issues have been created, but there are problems in adding them to the page. You can manually add them later using JIRA macro.{quote} The following will appear in the logs as well: {code} 2014-09-17 13:16:09,661 WARN [http-bio-8091-exec-1] [internal.integration.jira.DefaultJiraService] communicateWithJira Problem communicating with JIRA -- referer: http://new.com/display/WEB/test | url: /teamsite/rest/jira-integration/1.0/issues | userName: van.ly com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:376) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:161) {code} h3.Workaround The only available workaround is to manually add JIRA issue links to the page.

    Atlassian JIRA | 2 years ago | Jing Hwa [Atlassian]
    com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out
  6. 0

    [BAM-16239] Bamboo should support the use of TLS - SNI - Atlassian JIRA

    atlassian.com | 1 year ago
    com.atlassian.sal.api.net.ResponseException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.atlassian.sal.api.net.ResponseException

      java.net.SocketTimeoutException: Read timed out

      at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn()
    2. com.atlassian.sal
      HttpClientRequest.executeAndReturn
      1. com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:376)
      1 frame
    3. com.atlassian.plugins
      JerseyRequest.executeAndReturn
      1. com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:161)
      1 frame
    4. com.atlassian.applinks
      ThreeLeggedOAuthRequest.execute
      1. com.atlassian.applinks.core.auth.ApplicationLinkRequestAdaptor.execute(ApplicationLinkRequestAdaptor.java:84)
      2. com.atlassian.applinks.core.auth.oauth.ThreeLeggedOAuthRequest.execute(ThreeLeggedOAuthRequest.java:54)
      2 frames
    5. com.atlassian.internal
      JiraServerResource.getProjectsMeta
      1. com.atlassian.internal.integration.jira.DefaultJiraService$5.apply(DefaultJiraService.java:451)
      2. com.atlassian.internal.integration.jira.DefaultJiraService$5.apply(DefaultJiraService.java:445)
      3. com.atlassian.internal.integration.jira.DefaultJiraService.communicateWithJira(DefaultJiraService.java:702)
      4. com.atlassian.internal.integration.jira.DefaultJiraService.getProjectsAsJson(DefaultJiraService.java:445)
      5. com.atlassian.internal.integration.jira.rest.JiraServerResource.getProjectsMeta(JiraServerResource.java:43)
      5 frames
    6. Java RT
      Method.invoke
      1. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      2. sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      3. sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      4. java.lang.reflect.Method.invoke(Method.java:606)
      4 frames