|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Thanks everyone for attaching the stack trace, but you are cutting out the crucial part of the stack trace! Specifically, we need to see "unexportByOid2nd 2nd unexport attempt is here" message that immediately follows this.
I've subsequently made this fix in remoting 2.42 that I believe fixes the majority of these problems. Check if you have any slave that's running slave.jar older than 2.42, and upgrade.
If you continue to see this problem despite slave.jar being newer, please attach the whole stack traces — 2 of them to be exact.