|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-14782) SCM polling cripples ... [email protected] (JIRA)
- [JIRA] (JENKINS-14782) SCM polling crip... [email protected] (JIRA)
- [JIRA] (JENKINS-14782) SCM polling crip... [email protected] (JIRA)
- [JIRA] (JENKINS-14782) SCM polling crip... [email protected] (JIRA)
- [JIRA] (JENKINS-14782) SCM polling crip... [email protected] (JIRA)
- [JIRA] (JENKINS-14782) SCM polling crip... [email protected] (JIRA)
- [JIRA] (JENKINS-14782) SCM polling crip... [email protected] (JIRA)
- [JIRA] (JENKINS-14782) SCM polling crip... [email protected] (JIRA)
- [JIRA] (JENKINS-14782) SCM polling crip... [email protected] (JIRA)

It's just waiting for perforce to finish it's operation. I'm not sure how this would cripple your server. How many polling threads do you have?
You may want to check out the p4 processes running on the machine using truss or something similar to see what it's up to.