Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-61762

Intermittent Socket closed or Read timed out error

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Not A Defect
    • jira-steps-plugin
    • Jenkins Version:2.204.5 (Docker image)
      JIRA Pipeline Steps :1.5.3
      Web browser : Google Chrome
      Java Version: 1.8

    Description

      jiraEditIssue, jiraNewIssue and  jiraJqlSearch  are some time failing with "Socket Closed" or "Read timed out" error.

       

       

      JIRA: Site - JIRA-PROD - Updating issue: Ticket-1234
      Error Code: -1
      Error Message: Socket closed
      [Pipeline] }
      [Pipeline] // script
      Error when executing always post condition:
      hudson.AbortException: Socket closed
      	at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132)
      	at org.thoughtslive.jenkins.plugins.jira.steps.EditIssueStep$Execution.run(EditIssueStep.java:80)
      

       

      JIRA: Site - JIRA-PROD - Creating new issue: IssueInput(update=null, fields={project={key=REI}, summary=Build Error., description=New JIRA Created from Jenkins., issuetype={name=Bug}})
      Error Code: -1
      Error Message: Socket closed
      [Pipeline] }
      [Pipeline] // script
      Error when executing regression post condition:
      hudson.AbortException: Socket closed
      	at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132)
      	at org.thoughtslive.jenkins.plugins.jira.steps.NewIssueStep$Execution.run(NewIssueStep.java:84)
      	at org.thoughtslive.jenkins.plugins.jira.steps.NewIssueStep$Execution.run(NewIssueStep.java:53)
      	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      

       

      JIRA: Site - JIRA-PROD - Search JQL: project = "Release Engineering Internal"   AND description ~ "New JIRA Created from Jenkins" ORDER BY id DESC startAt: 0 maxResults: 1
      Error Code: -1
      Error Message: Read timed out
      [Pipeline] }
      [Pipeline] // script
      Error when executing failure post condition:
      hudson.AbortException: Read timed out
      	at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132)
      	at org.thoughtslive.jenkins.plugins.jira.steps.JqlSearchStep$Execution.run(JqlSearchStep.java:89)
      	at org.thoughtslive.jenkins.plugins.jira.steps.JqlSearchStep$Execution.run(JqlSearchStep.java:65)
      	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      

      Attachments

        Activity

          Socket timeout or read timed out occur when the actual server isn't responding within the given time, you configure site on global section with increased timeout settings. Here is the example screenshot.

          nrayapati Naresh Rayapati added a comment - Socket timeout or read timed out occur when the actual server isn't responding within the given time, you configure site on global section with increased timeout settings. Here is the example screenshot.

          Naresh,

          Increased the Socket timeout or read timed at the global section is increased from 10 Seconds to 60 Seconds.
          I works now.

          Thanks a lot.

           

          Shivaji

          shivaji_thanneeru Shivaji Thanneeru added a comment - Naresh, Increased the Socket timeout or read timed at the global section is increased from 10 Seconds to 60 Seconds. I works now. Thanks a lot.   Shivaji

          People

            nrayapati Naresh Rayapati
            shivaji_thanneeru Shivaji Thanneeru
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: