|
||||||||
|
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)

I having a tough time understanding what the actual issue is. Does Tomcat start using 100% cpu, or does it just sit there doing nothing? If it's the latter, then I can't see how polling would be affect the entire application server like that.
Have you checked the p4 processes to make sure they aren't hanging?