Java process not killed and File descriptor not free

[romain.guilloux]

Hi,

    I observed that NSO didn't kill some java process and didn't free all file descriptor after executing commands (such as a simple check_sync in cli). Is it a behaviour known, will it be a risk in a production environment ? I have a NSOv4.6 (server installation on centos) where the file descriptor is already at 16000 ? The only solution I find is to stop NSO an restart it and it free process and file descriptor, do you have some advise ?

rguilloux@vm:~/NSO/ncs-run-4.6$ lsof -p $(pgrep ncs.smp) | wc -l
143
rguilloux@vm:~/NSO/ncs-run-4.6$ lsof -p $(pgrep ncs.smp) | wc -l
143
rguilloux@vm:~/NSO/ncs-run-4.6$ lsof -p $(pgrep ncs.smp) | wc -l
181
rguilloux@vm:~/NSO/ncs-run-4.6$ lsof -p $(pgrep ncs.smp) | wc -l
181

evolution of file descriptor in time when performing check_sync, stop/start nso in time

Thanks.

[ynagami · Accepted solution]

As far as I know, Generally NSO has device session pool. Once NSO connects devices, it is maintained for a while.

See also:

<NSO installation directory>doc/html/nso_user_guide/user_guide.devicemanager.pooling.html

And NSO may also consume FD in order to write device trace log file. it is also maintained as well as session pooling.

See also:

<NSO installation directory>/doc/html/nso_user_guide/user_guide.devicemanager.tracing.html