|
||||||||
|
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.
Latest Jenkins ver. 1.563 still exhibits this issue. I've see this exception ~500 times (according to jenkins' master logs) in the last 24hrs of running 1.563.
My setup was hit pretty hard by https://issues.jenkins-ci.org/browse/JENKINS-22734, and the stability in 1.563 is considerably improved (thanks!), but the java -jar /tmp/slave.jar process on EC2 (3.10.38-49.136.amzn1.x86_64 + java-1.7.0_55) slaves still dies occasionally. It seems to happen more frequently on jobs that produce a lot of verbose, debugging output.
At this point, I'm unsure if this issue (SEVERE: Trying to unexport an object that's already unexported) is actually the cause of the slave.jar process dying or just a coincidental occurrence.
Open to suggestions as to how to provide better debugging information. Happy to help in any way I can.