In general, you don't need to fix the message that the process leaked file descriptors. If the process leaks file descriptors, eventually it will exhaust the file descriptors, but that is not likely the cause of a problem for this specific job.
If you want processes to survive beyond the end of a job, then there are additional steps you need to take. Refer to https://wiki.jenkins.io/display/JENKINS/Spawning+processes+from+build for techniques to keep a process running after the Jenkins job is complete. Mark Waite On Friday, June 23, 2017 at 12:57:19 AM UTC-6, parvatha reddy wrote: > > > mark, > > I did run Jenkins job in executing windows batch command. But Jenkins job > itself kill all the child process.due to Runtime Environment will be down. > can you please help us, how I can fix process leaked file descriptors > issue. > execute shell the command: > N: > cd CCOP\REFRESH_SCRIPTS > rebuild_env.cmd %EnvType% > > > Process leaked file descriptors. See > http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for > more information > Triggering a new build of YP ยป Runtime stop and restart on ST1 > <http://illin187:4143/jenkins/job/YP/job/Runtime%20stop%20and%20restart%20on%20ST1/> > > > Finished: SUCCESS > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/94db626c-2815-489a-b73c-45f2a27b5a8e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
