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

jiraJqlSearch Error Message: Socket closed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Component/s: jira-steps-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.89.4
      jira-steps - 1.31
    • Similar Issues:

      Description

      If the number of records returned is small this query is successful but once the number is greater than ~100 the below error is thrown.

      I've verified that the JIRA restapi is successfully returning the correct results.  My jira-steps timeouts have been set to 1000s. The jenkins job is failing ~20 seconds
      [Pipeline] jiraJqlSearch
      JIRA: Site - Jira01 - Search JQL: <JQL> startAt: 0 maxResults: 1000
      Error Code: -1
      Error Message: Socket closed
       

        Attachments

          Issue Links

            Activity

            Hide
            nrayapati Naresh Rayapati added a comment - - edited

            Dave Rogers: Thanks for reporting.

            Refer to https://issues.jenkins-ci.org/browse/JENKINS-49314, that enhancement would give us a functionality to adjust the readTimeOut, which is currently configured to 10000.

            Best practice is to limit the number of JIRAs queried through JQL to avoid the unexpected load on the JIRA Server. I would use startAt and maxResults to query results incrementally instead.

            This isn't a bug, minor enhancement, in fact is a duplicate with JENKINS-49314. If you agree I would close it.

            Show
            nrayapati Naresh Rayapati added a comment - - edited Dave Rogers : Thanks for reporting. Refer to https://issues.jenkins-ci.org/browse/JENKINS-49314 , that enhancement would give us a functionality to adjust the readTimeOut, which is currently configured to 10000. Best practice is to limit the number of JIRAs queried through JQL to avoid the unexpected load on the JIRA Server. I would use startAt and maxResults to query results incrementally instead. This isn't a bug, minor enhancement, in fact is a duplicate with JENKINS-49314 . If you agree I would close it.
            Hide
            drogers Dave Rogers added a comment -

            Thanks for the fast response Naresh.

            I need to run large queries  on our corporate Jira server which is a little slow.

             

            I did read review JENKINS-49314 but I was unclear if this was the same issue.

            I believe this to be a bug as if the plugin errors out on a query which can run successfully via the restapi then it's an issue with the plugin

            Thanks again I'll close this ticket.

             

            Show
            drogers Dave Rogers added a comment - Thanks for the fast response Naresh. I need to run large queries   on our corporate Jira server which is a little slow.   I did read review  JENKINS-49314  but I was unclear if this was the same issue. I believe this to be a bug as if the plugin errors out on a query which can run successfully via the restapi then it's an issue with the plugin Thanks again I'll close this ticket.  
            Hide
            drogers Dave Rogers added a comment -

            Thanks again

            Dave

            Show
            drogers Dave Rogers added a comment - Thanks again Dave

              People

              • Assignee:
                nrayapati Naresh Rayapati
                Reporter:
                drogers Dave Rogers
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: