[
https://issues.jenkins-ci.org/browse/JENKINS-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160676#comment-160676
]
Guido Serra commented on JENKINS-5413:
--------------------------------------
Hi, I got the same issue:
- Jenkins GIT 1.1.16
- Slave: Windows 7, msysgit (Git-1.7.9-preview20120201.exe)
After I moved the SCM from SVN to the Git solution, the poll/build stopped
working
This is how I got the windows machine being able to checkout git with
ssh/publickey:
- http://guidoserra.it/archivi/2012/03/22/jenkins-msysgit-publickey/
p.s. I was even thinking of using Fisheye to trigger the build on code change
detection
> SCM polling on slaves getting hung
> ----------------------------------
>
> Key: JENKINS-5413
> URL: https://issues.jenkins-ci.org/browse/JENKINS-5413
> Project: Jenkins
> Issue Type: Bug
> Components: master-slave
> Affects Versions: current
> Reporter: Dean Yu
> Attachments: hung_scm_pollers_02.PNG, threads.vetted.txt,
> thread_dump_02.txt
>
>
> This is to track the problem originally reported here:
> http://n4.nabble.com/Polling-hung-td1310838.html#a1310838
> The referenced thread is relocated to
> http://jenkins.361315.n4.nabble.com/Polling-hung-td1310838.html
> What the problem boils down to is that many remote operations are performed
> synchronously causing the channel object to be locked while a response
> returns. In situations where a lengthy remote operations is using the
> channel, SCM polling can be blocked waiting for the monitor on the channel to
> be released. In extreme situations, all the polling threads can wind up
> waiting on object monitors for the channel objects, preventing further
> processing of polling tasks.
> Furthermore, if the slave dies, the locked channel object still exists in the
> master JVM. If no IOException is thrown to indicate the termination of the
> connection to the pipe, the channel can never be closed because
> Channel.close() itself is a sychronized operation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
