Status: Resolved (View Workflow)
Ssince recently we are running in a 'too many open files' issue on our jnlp agent build nodes (the Jenkins server itself is fine). All the file descriptors 'leaking' are for the junit/surefire reports of our maven builds. Disabling the junitParser from the warnings-ng-plugin seems to resolve the issue.
Browsing the code I wonder if there is a close call missing in the JunitAdapter count method (analysis model plugin: https://github.com/jenkinsci/analysis-model/blob/master/src/main/java/edu/hm/hafner/analysis/parser/violations/JUnitAdapter.java#L45). Other calls to readStream seem to be wrapped in a try-with-resources, like https://github.com/jenkinsci/analysis-model/blob/master/src/main/java/edu/hm/hafner/analysis/parser/AjcParser.java#L30.
|Field||Original Value||New Value|
|Assignee||Ulli Hafner [ drulli ]||Sverre Boschman [ sverre_boschman ]|
|Resolution||Fixed [ 1 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|