I encountered a very similar issue, yet I have a slightly different setup:

  • 1 master 1 slave
  • yet the polling was stuck on the master only
  • SCM polling hanging (warning displayed in Jenkins configure screen). Oldest hanging thread is more than 2 days old.
  • it seems it all started with a Unix process that in some way never returned:
ps -aef| grep jenkins 
  300 12707     1   0 26Nov12 ??       1336:33.09 /usr/bin/java -Xmx1024M -XX:MaxPermSize=128M -jar /Applications/Jenkins/jenkins.war
  300 98690 12707   0 Sat03PM ??         0:00.00 git fetch -t https://github.com/jenkinsci/testflight-plugin.git +refs/heads/*:refs/remotes/origin/*
  300 98692 98690   0 Sat03PM ??         4:39.72 git-remote-https https://github.com/jenkinsci/testflight-plugin.git https://github.com/jenkinsci/testflight-plugin.git
    0  3371  3360   0  8:20PM ttys000    0:00.02 su jenkins
  300  4017  3372   0  8:52PM ttys000    0:00.00 grep jenkins
    0 10920 10896   0 19Nov12 ttys001    0:00.03 login -pfl jenkins /bin/bash -c exec -la bash /bin/bash

Running Jenkins 1.479

I killed the processes and associated threads, and it started being better.

Polling doesn't enfore timeouts ?

Change By: lacostej (14/Jan/13 8:15 PM)
Attachment: DUMP1.txt
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

Reply via email to