|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
As an update for information we have started to correlate the increases in threads potentially to a particular type of job we use. It might be related to the Execute remote commands via SSH build step, though I don't have enough proof. We found this stack overflow link: http://stackoverflow.com/questions/11300857/how-many-threads-should-jenkins-run which led us to look for jobs that might not be properly returning an exit status.
The timings of when threads spike the most vs when those jobs run is close. Those jobs SSH into a remote server adn execute a long running script that basically runs an rsync of files to another machine that can occasionally fail. It's not clear yet how the exit codes are handled, the job itself completes successfully. We need to dig more. It is painfully difficult to understand when/why Jenkins would create a pool-XXXXX-thread.