|
||||||||
|
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 the latter. We are also suspecting the current p4 command line client, and we will be upgrading it. There have been no I/O issues that we could see. What confuses is me is how a forked process could be making Tomcat grind to a halt and leave the rest of the box unaffected, unless it's a deeper systemic issue, but where that the case, we would have had far worse problems than this. I will let you know what happens as soon as we upgrade the p4 binary and re-test