|
||||||||
|
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/groups/opt_out.
A rough, untested how-to for those willing to try the attached patch, who are not familiar with building the jar:
0. have a JDK, maven (I used maven 2, not sure if maven 3 works too) and (optionally) git properly installed
1. Get sources from https://github.com/jenkinsci/remoting/tree/remoting-2.17
2. Apply the patch
3. Build (mvn package) to get your custom remoting-2.17.jar
4. Stop Jenkins
5. To use this on Master (which is where problem occurs), go to folder ...jenkins/war/WEB-INF/lib, and replace existing remoting*.jar with the one you built
6. Optionally, to use this also on slaves where Jenkins copies the .jar file to slave, go to folder ...jenkins/war/WEB-INF, and replace existing remoting.jar and slave.jar with the one you built.
7. Restart Jenkins, look at log files, search for "interrupthack" string to find stuff logged by the patch.