|
||||||||
|
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.
The version of Jenkins running is 1.559. The problem occurs on both the master and the slaves, I did note the earlier OOME problem which is what prompted to me to upgrade the ant jar in the lib directory but this hasn't resolved the issue.
We haven't changed anything (to my knowledge) which is what is the most peculiar, jobs just started failing with this error.
I don't have either the monitoring plugin installed nor heap dumps right now. Looking on our monitoring dashboards I can see sufficient memory available, GCs are ok (no loitering objects).
All I can say is that by removing the Archive Artifacts step all builds are then successful. Adding it back in causes the error to appear straight away.
I will try and get a heap dump after one of the failed runs.