[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1

[dan...@danielgrunwald.de (JIRA)]

Title: Message Title

Daniel Grunwald created an issue   Jenkins / JENKINS-61823 "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 Issue Type: Bug Assignee: Unassigned Components: winstone-jetty Created: 2020-04-06 12:49 Priority: Minor Reporter: Daniel Grunwald After upgrading from Jenkins 2.204.2 to 2.222.1, our builds started failing non-deterministically when trying to download artifacts. It seems that Jenkins no longer honors the "--httpKeepAliveTimeout=60000" switch. I confirmed that Jenkins is running with switch. Yet a download with a slow consumer will fail with a partial download. (for testing: "curl -f -u $jenkins_auth $artifact_url | (sleep 6; wc -c)"  On the server side, the log indicates that the command-line switch was ineffective and the default 5s timeout is still in use: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171) at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) Caused: java.io.IOException at org.eclipse.jetty.util.SharedBlockingCallback$Blocker.block(SharedBlockingCallback.java:234) at org.eclipse.jetty.server.HttpOutput.channelWrite(HttpOutput.java:268) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:825) at org.kohsuke.stapler.Stapler.serveStaticResource(Stapler.java:612) at org.kohsuke.stapler.ResponseImpl.serveFile(ResponseImpl.java:216) at hudson.model.DirectoryBrowserSupport.serveFile(DirectoryBrowserSupport.java:370) at hudson.model.DirectoryBrowserSupport.generateResponse(DirectoryBrowserSupport.java:155) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:164) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:147) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) The default 5s timeout is short enough that a simple "curl | tar xf" sometimes trips it when unpacking many small files on an overloaded VM. Please consider changing the default back to jetty's 30s. Add Comment   This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205673.1586177353000.6962.1586177400098%40Atlassian.JIRA.