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

Getting ERR_EMPTY_RESPONSE when saving configuration

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: core
    • Labels:
    • Environment:
      Jenkins 2.277.3 on Windows Server 2019
    • Similar Issues:
    • Released As:
      2.289.2

      Description

      We're seeing this intermittent problem when trying trying to save a job configuration. When hitting Save Chrome is simply throwing an ERR_EMPTY_RESPONSE message.

      Having done some investigation it seems the error is only present when the content length of the post request to configSubmit is larger than 16000. Anything smaller than that and the save works successfully. 

      Is there a  maxPostSize parameter or something similar that can be configured?

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          There was an issue in Jenkins 2.277.3 and Jenkins 2.289.1 related to the Jetty component that handles HTTP. See JENKINS-65667 and JENKINS-65624 for more details of the failure modes. The solution in those cases was to update to Jenkins 2.289.2. It includes a more recent version of Jetty.

          Is the problem resolved if you update to Jenkins 2.289.2?

          Show
          markewaite Mark Waite added a comment - There was an issue in Jenkins 2.277.3 and Jenkins 2.289.1 related to the Jetty component that handles HTTP. See JENKINS-65667 and JENKINS-65624 for more details of the failure modes. The solution in those cases was to update to Jenkins 2.289.2. It includes a more recent version of Jetty. Is the problem resolved if you update to Jenkins 2.289.2?
          Hide
          chrisedgington Chris added a comment -

          Mark Waite thanks very much. Upgrading to 2.289.2 has indeed resolved our issue.

          Show
          chrisedgington Chris added a comment - Mark Waite  thanks very much. Upgrading to 2.289.2 has indeed resolved our issue.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            chrisedgington Chris
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: