How do I resolve the Jenkins error: "Process leaked file descriptors" when using the lscm command?
We have a Jenkins job that calls the lscm Windows batch script to log in to RTC. When running the Jenkins job however, we receive the error: "Process leaked file descriptors". This error also appears when running any other lscm command like logout and load. I've tried putting the lscm commands into a separate batch file but I get the same result. Any help would be appreciated. Thanks.
Comments
Donald Nong
Oct 01 '13, 9:31 p.m.Based on some comment about how this error gets generated, it seems the behavior is expected?
https://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
Basically when you run lscm, it does spawn a process (the daemon). This may make Jenkins to believe it is a "problem", hence the error.
To verify this, you can try replace "lscm" with "scm". The difference between these two commands is mainly the daemon - no daemon for "scm".
Jeffrey Cheng
Oct 02 '13, 3:24 p.m.Using the "scm" command seems to work now, thanks. Are there any downsides to using "scm" rather than "lscm"?
Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Oct 03 '13, 11:41 a.m.scm is slower, because it needs to reload all the eclipse libraries to execute the command (instead of sending the request to a running daemon, as is done by lscm). But otherwise, the functionality is identical.