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

Timeout not working

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • sitemonitor-plugin
    • None
    • CentOS 5.6; Sun Java 1.6.0_26

    Description

      Twice now I've had jobs hang because sitemonitor was waiting for a response from the server.
      Stop/starting the server in question allowed the job to complete.

      In both cases, a 503 response code was recorded to the console.

      My timeout is set to the default.

      Attachments

        Activity

          rinok Rino added a comment -

          We had to do the following to remove jobs from the queue:

          download the jenkins command line interface from your buildserver: http://yourbuildserver/jenkins/cli

          java -jar jenkins-cli.jar -s http://yourbuildserver/jenkins/ login --username yourusername --password yourpassword

          java -jar jenkins-cli.jar -s http://yourbuildserver/jenkins/ delete-builds Name_Of_Job Build_Number_You_Want_To_Delete

          rinok Rino added a comment - We had to do the following to remove jobs from the queue: download the jenkins command line interface from your buildserver: http://yourbuildserver/jenkins/cli java -jar jenkins-cli.jar -s http://yourbuildserver/jenkins/ login --username yourusername --password yourpassword java -jar jenkins-cli.jar -s http://yourbuildserver/jenkins/ delete-builds Name_Of_Job Build_Number_You_Want_To_Delete
          medington Mark Edington added a comment - - edited

          This issue appears to be addressed by Pull Request #7.

          I built and tested this fix and it solved the issue where the connection is successful, but the server fails to return a response in a reasonable amount of time.

          For reference, here is how the mis-behaving server I'm dealing with looks like via curl:

          curl output
          curl -v -I -m 10 'http://10.21.0.216:8983/solr/wanderful1/select?q=id:1&rows=0&wt=json'
          * About to connect() to 10.21.0.216 port 8983 (#0)
          *   Trying 10.21.0.216...
          * Adding handle: conn: 0x7fb9b3004400
          * Adding handle: send: 0
          * Adding handle: recv: 0
          * Curl_addHandleToPipeline: length: 1
          * - Conn 0 (0x7fb9b3004400) send_pipe: 1, recv_pipe: 0
          * Connected to 10.21.0.216 (10.21.0.216) port 8983 (#0)
          > HEAD /solr/wanderful1/select?q=id:1&rows=0&wt=json HTTP/1.1
          > User-Agent: curl/7.30.0
          > Host: 10.21.0.216:8983
          > Accept: */*
          >
          * Operation timed out after 10138 milliseconds with 0 out of -1 bytes received
          * Closing connection 0
          curl: (28) Operation timed out after 10138 milliseconds with 0 out of -1 bytes received
          
          medington Mark Edington added a comment - - edited This issue appears to be addressed by Pull Request #7 . I built and tested this fix and it solved the issue where the connection is successful, but the server fails to return a response in a reasonable amount of time. For reference, here is how the mis-behaving server I'm dealing with looks like via curl: curl output curl -v -I -m 10 'http://10.21.0.216:8983/solr/wanderful1/select?q=id:1&rows=0&wt=json' * About to connect() to 10.21.0.216 port 8983 (#0) * Trying 10.21.0.216... * Adding handle: conn: 0x7fb9b3004400 * Adding handle: send: 0 * Adding handle: recv: 0 * Curl_addHandleToPipeline: length: 1 * - Conn 0 (0x7fb9b3004400) send_pipe: 1, recv_pipe: 0 * Connected to 10.21.0.216 (10.21.0.216) port 8983 (#0) > HEAD /solr/wanderful1/select?q=id:1&rows=0&wt=json HTTP/1.1 > User-Agent: curl/7.30.0 > Host: 10.21.0.216:8983 > Accept: */* > * Operation timed out after 10138 milliseconds with 0 out of -1 bytes received * Closing connection 0 curl: (28) Operation timed out after 10138 milliseconds with 0 out of -1 bytes received
          medington Mark Edington added a comment - - edited

          I have a 2 line fix for this (setting the read timeout on the connection), shall I submit a pull request? The fix in Pull Request #7 involves quite bit more code change. It's not clear on what is gained from invoking the URL asynchronously.

          medington Mark Edington added a comment - - edited I have a 2 line fix for this (setting the read timeout on the connection), shall I submit a pull request? The fix in Pull Request #7 involves quite bit more code change. It's not clear on what is gained from invoking the URL asynchronously.

          People

            cliffano cliffano
            ganncamp G. Ann Campbell
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: