Change By: Damon G (26/Jun/14 11:46 AM)
Description: We can run for about 2 days and then the system basically becomes unresponsive and needs to be restarted.

Everything was going fine for many months at version 1.5.46 but once we went to 1.5.66 or 1.5.68 we begin to see too many open files exceptions until jenkins needed a restart.  Attached are the stack traces. I didn't choose a specific component because I wasn't sure which component to log it against. I also don't see any existing open issues that match this. Hope opening this was valid.

I've attached a list of all files opened (using lsof) by jenkins as well as the jenkins log containing the stack traces.

I only included a couple of the stack traces because I have a feeling the output of lsof may be more illuminating.

Happy to provide anything more you need. This is one of my first defects so I hope I'm giving enough detail without it already being a known issue.

----Update-----
We did an experiement where we repeatedly ran the jenkins cli. We did this because our jenkins jobs utilize it heavily and we were suspicious it might be related. For every jenkins cli command executed generated another open file reference that doesn't appear to get closed.




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.

Reply via email to