Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-34808] - Allow user to adjust socket timeout #68

Merged
merged 1 commit into from
Apr 20, 2016

Conversation

fengxx
Copy link

@fengxx fengxx commented Jan 29, 2016

we encounter slave offline issue when executing commands like
sleep 40m
on jnlp agent, the socket read timeout is hard coded to 30 minutes and caused the issue

@jenkinsadmin
Copy link
Member

Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests.

@fengxx
Copy link
Author

fengxx commented Jan 29, 2016

the build was aborted for exceeding build time limit (8 minutes), maybe caused by slow maven download. I don't think the commit will affects the build

@@ -403,6 +403,8 @@ public static Engine current() {

private static final Logger LOGGER = Logger.getLogger(Engine.class.getName());

static final int TIMEOUT = Integer.getInteger(Engine.class.getName()+".soTimeout",30*60*1000);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe "socketTimeout"? Readability is better than economy on several symbols :)

@oleg-nenashev
Copy link
Member

merge conflict

@oleg-nenashev
Copy link
Member

I want to make the timeout configurable before the next version release

@fengxx
Copy link
Author

fengxx commented Feb 23, 2016

Thanks for reviewing, I had renamed it to socketTimeout

@oleg-nenashev oleg-nenashev changed the title allow user to adjust socket timeout Allow user to adjust socket timeout Apr 20, 2016
@oleg-nenashev oleg-nenashev merged commit 30dc0dd into jenkinsci:master Apr 20, 2016
@oleg-nenashev
Copy link
Member

Subject for a backporting. I'll create an issue

@oleg-nenashev
Copy link
Member

@oleg-nenashev oleg-nenashev changed the title Allow user to adjust socket timeout [JENKINS-34808] - Allow user to adjust socket timeout May 13, 2016
oleg-nenashev added a commit to oleg-nenashev/jenkins that referenced this pull request May 13, 2016
Changes:
* [JENKINS-34213](https://issues.jenkins-ci.org/browse/JENKINS-34213) - Ensure that the unexporter cleans up whatever it can each sweep (jenkinsci/remoting#81)
* [JENKINS-19445](https://issues.jenkins-ci.org/browse/JENKINS-19445) Force class load on UserRequest in order to prevent deadlock on windows nodes when using JNA and Subversion (jenkinsci/remoting#81)
* [JENKINS-34808](https://issues.jenkins-ci.org/browse/JENKINS-34808) - Allow user to adjust socket timeout (jenkinsci/remoting#68)
oleg-nenashev added a commit to jenkinsci/jenkins that referenced this pull request May 14, 2016
…oting to 2.59. (#2344)

* [JENKINS-19445, JENKINS-34213, JENKINS-34808] Bump remoting to 2.58.

Changes:
* [JENKINS-34213](https://issues.jenkins-ci.org/browse/JENKINS-34213) - Ensure that the unexporter cleans up whatever it can each sweep (jenkinsci/remoting#81)
* [JENKINS-19445](https://issues.jenkins-ci.org/browse/JENKINS-19445) Force class load on UserRequest in order to prevent deadlock on windows nodes when using JNA and Subversion (jenkinsci/remoting#81)
* [JENKINS-34808](https://issues.jenkins-ci.org/browse/JENKINS-34808) - Allow user to adjust socket timeout (jenkinsci/remoting#68)

* [JENKINS-34121] - Upgrade remoting to 2.59
oleg-nenashev added a commit to oleg-nenashev/jenkins that referenced this pull request May 17, 2016
…oting to 2.59

Changes:

2.58:
* [JENKINS-34213](https://issues.jenkins-ci.org/browse/JENKINS-34213) - Ensure that the unexporter cleans up whatever it can each sweep (jenkinsci/remoting#81)
* [JENKINS-19445](https://issues.jenkins-ci.org/browse/JENKINS-19445) Force class load on UserRequest in order to prevent deadlock on windows nodes when using JNA and Subversion (jenkinsci/remoting#82)
* [JENKINS-34808](https://issues.jenkins-ci.org/browse/JENKINS-34808) - Allow user to adjust socket timeout (jenkinsci/remoting#68)

2.59:
* [JENKINS-34819](https://issues.jenkins-ci.org/browse/JENKINS-34819) - Allow disabling the remoting protocols individually. Works around issues like [JENKINS-34121](https://issues.jenkins-ci.org/browse/JENKINS-34121) (jenkinsci/remoting#83)
olivergondza pushed a commit to jenkinsci/jenkins that referenced this pull request May 25, 2016
…oting to 2.59. (#2344)

* [JENKINS-19445, JENKINS-34213, JENKINS-34808] Bump remoting to 2.58.

Changes:
* [JENKINS-34213](https://issues.jenkins-ci.org/browse/JENKINS-34213) - Ensure that the unexporter cleans up whatever it can each sweep (jenkinsci/remoting#81)
* [JENKINS-19445](https://issues.jenkins-ci.org/browse/JENKINS-19445) Force class load on UserRequest in order to prevent deadlock on windows nodes when using JNA and Subversion (jenkinsci/remoting#81)
* [JENKINS-34808](https://issues.jenkins-ci.org/browse/JENKINS-34808) - Allow user to adjust socket timeout (jenkinsci/remoting#68)

* [JENKINS-34121] - Upgrade remoting to 2.59

(cherry picked from commit 409438f)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants