-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.util.ArrayList$Itr error when using the orchestration pipeline #745
Comments
In a new project, I run developer preview just the 2º time and we get this error. |
@braisvq1996 this is an effect of Jenkins running out of memory. Don’t forget to adjust also the Java heap size on the Jenkins master next to increasing me key on the pod itself. |
Yeah, the JAVA_MAX_HEAP_PARAM for the Jenkins container where it failed was -Xms10g -Xmx18g. The container has 20 GB as memory limit |
@braisvq1996 - can you repro this? wehave to fix this - no way a jenkins needing 20! gigs ... a) component pipeline: https://github.com/opendevstack/ods-jenkins-shared-library/blob/master/src/org/ods/component/Context.groovy#L528 This is super easy to refactor into its own method and flag with NonCPS b) finalize ods component: https://github.com/opendevstack/ods-jenkins-shared-library/blob/master/src/org/ods/orchestration/phases/FinalizeOdsComponent.groovy#L73 this is super weird as this runs on an agent I believe - and there is no functional loop anywhere ... (correction: there is, but could this really be it?) : https://github.com/opendevstack/ods-jenkins-shared-library/blob/master/src/org/ods/orchestration/FinalizeStage.groovy#L65 which is the call stack parent of the above call |
There mus be a memory leak somewhere as well btw ... |
Ok . more digging - I think we have to refactor: to use classical for loops - or get them really into NonCPS annotated methods... |
plan of action: |
@metmajer - we uncovered two issues, but where able to run 3 repos (2 ods-code / 1 e2e spock) with all docs and it worked (with 4gig and 3 requested :)) |
@braisvq1996 - as discussed please test a couple of more runs of this combo - so we really see if there is not more to fix. @metmajer - fyi |
we are stuck with the component pipeline (we get the $Itr - seriously at the script.sh!) @michaelsauter any ideas? after fixing all sorts of issues - we are really stuck here ... (jenkins bug?) |
I looked at the source code right now but I do not understand how that line could produce an exception that |
@michaelsauter - it's coming from that line (we have surrounded this now with a try {} block, it's coming definetely from there) the callstack - is coming from I am inclined to believe this to be a jenkins bug ... but I cannot pinpoint it (unfortunately) .. |
so - with a while & sleep it seems to work ... :( Tmrw we'll stick even more stories++ into jira to see if there is more we missed ... |
with the changes on #980 and opendevstack/ods-core#1217 we do not have more memory issues with Jenkins so issue can be closed |
Describe the bug
We have a project that is using a huge amount of resources for theis Jenkins-master instance (20 GB and JVM is -Xms10g -Xmx18g) in order to aboid this error, but it still appear from time to time when running developer previews.
I have only seen this if document generation is enabled.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The execution of the orchestration pipeline with document generation should not fail
Screenshots
Resources usage when error happened:
Log where the error took place):
Another log where the error happened:
Affected version (please complete the following information):
The text was updated successfully, but these errors were encountered: