[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Daniel Grunwald updated an issue Jenkins / JENKINS-61823 "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 Change By: Daniel Grunwald Priority: Minor Critical 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.7019.1586181480134%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Daniel Grunwald commented on JENKINS-61823 Re: "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 I downgraded to 2.204.6, and now my downloads are complete again. 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.7018.1586181420046%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Daniel Grunwald updated an issue Jenkins / JENKINS-61823 "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 Change By: Daniel Grunwald Environment: Debian 10 with jenkins from http://pkg.jenkins-ci.org/debian-stable 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.6964.1586177880068%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title
Daniel Grunwald updated an issue
Jenkins / JENKINS-61823
"--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Change By:
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=6" switch.I confirmed that Jenkins is running with this 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:{code}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){code}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.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
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=6" 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
[JIRA] (JENKINS-42513) Increase default keep-alive timeouts
Title: Message Title Daniel Grunwald commented on JENKINS-42513 Re: Increase default keep-alive timeouts It's not just "terrible connections"; it could also be a consumer being slow for another reason. We just ran into this issue with a shell script doing: curl -f $JENKINS/$JOB/artifact/binaries.tar.gz | tar xz Sometimes unpacking was too slow (due to high load on the VM) and Jenkins terminated the download. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.179440.1488823793000.18080.1571826480339%40Atlassian.JIRA.
[JIRA] [ssh-slaves-plugin] (JENKINS-23419) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF
Daniel Grunwald commented on JENKINS-23419 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF To anyone else with this problem: this error indicates that the slave process died unexpected. See https://wiki.jenkins-ci.org/display/JENKINS/Remoting+issue In my case, the slave JVM terminates because the slave machine ran out of memory; and I get an error log file in the slave's FS root. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
