|
||||||||||||||
|
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/d/optout.
Due to the age of the original report and the nature of the issue, I'm resolving this. I don't claim this report is invalid, or obsolete: comments clearly indicate similar issues still happen. However, troubleshooting ancient versions with numerous changes since doesn't help, and it's possible some of you are actually experiencing a different problem, leading to inconsistent/contradictory information posted here.
If something similar occurs on your installation, and you're using a recent version of Jenkins (no older than eight weeks at the time of the report), please file a new bug in this tracker. Choose the component remoting. Carefully read and follow the instructions on this wiki page:
https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue
Make sure to include thread dumps in your report, relevant log excerpts, Jenkins slave configuration, etc.
Thanks!