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

Warning getResponseBody, use getResponseBodyAsStream instead

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Spam gets pretty horrible in Jenkins error log file depending on amount of branches it has to check.

      jun. 01, 2017 1:00:01 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
      WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
      jun. 01, 2017 1:00:01 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody
      WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
      jun. 01, 2017 1:00:01 PM jenkins.branch.OrganizationFolder$OrganizationScan run
      INFO: BEA #20170601.130000 organization scan action completed: SUCCESS in 1 sec

        Attachments

          Issue Links

            Activity

            Hide
            byahia Bilel Yahia added a comment -

            we do have the same problem, and it matches with times when we have ressources (cou and memory) spikes.

            Show
            byahia Bilel Yahia added a comment - we do have the same problem, and it matches with times when we have ressources (cou and memory) spikes.
            Hide
            jamesdumay James Dumay added a comment -

            Resolved as part of JENKINS-43507 in 2.2

            Show
            jamesdumay James Dumay added a comment - Resolved as part of JENKINS-43507 in 2.2

              People

              • Assignee:
                amuniz Antonio Muñiz
                Reporter:
                casz Joseph Petersen
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: